[GRADLE-1720] no stack trace when dependency resolution fails awkwardly Created: 04/Aug/11 Updated: 04/Jan/13 Resolved: 16/Oct/11 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 1.0-milestone-4 |
| Fix Version/s: | 1.0-milestone-5 |
| Type: | Bug | ||
| Reporter: | Szczepan Faber | Assignee: | Adam Murdoch |
| Resolution: | Fixed | Votes: | 0 |
| Description |
|
When dependency resolution fails for some interesting reason (e.g. bug in ivy/wharf/other participating library) there's no stack trace but just an exception message. We should be able to see the stack trace at least in debug mode. See DefaultIvyDependencyResolver:81, resolveReport.getAllProblemMessages() is not good enough. It should possible to interrogate resolveReport and get the stack trace. |
| Comments |
| Comment by Adam Murdoch [ 04/Aug/11 ] |
|
Not much we can do about this, because the exception swallowing is happening in ivy. It's a common pattern ivy uses all over the place. |
| Comment by Szczepan Faber [ 04/Aug/11 ] |
|
Possibly. After quick glance through the code it felt possible to do via the current api, e.g. resolveReport.getConfigurationReport().getUnresolvedDependencies().getProblem(), etc. Not going to be beautiful, though. Also, not sure if it's worth the hassle. |