[GRADLE-1736] idea/eclipse plugin fails fast when some dependency is unresolved Created: 09/Aug/11 Updated: 04/Jan/13 Resolved: 06/Oct/11 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | None |
| Fix Version/s: | 1.0-milestone-5 |
| Type: | Bug | ||
| Reporter: | Szczepan Faber | Assignee: | Szczepan Faber |
| Resolution: | Fixed | Votes: | 0 |
| Description |
|
idea/eclipse plugin fails fast when some dependency is unresolved. This means that if there's a single unresolved dependency then none (zero) metadata files are generated. This is highly undesirable because even that there are unresolved dependencies the user may be interested in pulling the project into the IDE. This also affects the Tooling API - if a single dependency is unresolved the Tooling API will not create a model at all. Tooling API client may be interested in the model anyway, regardless if there are some unresolved dependencies. |
| Comments |
| Comment by Szczepan Faber [ 06/Oct/11 ] |
|
I'm resolving this issue because it is resolved in the master There're next steps worth implementing (e.g. model the unresolved dependencies explicitly in the tooling-api; try resolve dependencies from all related configurations instead of failing on the first one, etc.). However I suggest we tackle them as separate issues. |
