[GRADLE-2370] Idea plugin should fail if there are unresolved dependcies in the project Created: 30/Jun/12 Updated: 01/Aug/14 Resolved: 01/Aug/14 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 1.0 |
| Fix Version/s: | None |
| Type: | New Feature | ||
| Reporter: | Marcin Erdmann | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Issue Links: |
|
||||||||
| Description |
|
If there is a dependency that cannot be resolved in a project for which we generate an Idea project using idea plugin it is silently ignored. The outcome is that the idea project is generated and if you incorrectly specify a dependency you don't understand why the classes are not available in the IDE. I believe idea task should fail in such a situation. |
| Comments |
| Comment by Daz DeBoer [ 30/Jun/12 ] |
|
We specifically choose to be lenient wrt missing dependencies in our IDE tasks. This enables a user to generate a functional IDE project even if their Gradle build is not completely correct or functional. The user can then user their IDE to update the Gradle build file. Perhaps Gradle should spit out a warning about missing/incorrect dependencies when generating an IDE project file. Or maybe add some sort of strict mode for generation, although running 'gradle classes' would do the same thing. But I'm pretty sure we don't want 'gradle idea' to fail in this case. |
| Comment by Szczepan Faber [ 01/Jul/12 ] |
|
Daz is right - we have a different ticket for the missing warning. Cheers! |
| Comment by Marcin Erdmann [ 02/Jul/12 ] |
|
For now I will use gradle classes before calling gradle idea to make sure that my dependencies are correct, but a warning would be much more convenient. Thanks for your responses. |