[GRADLE-34] Offer a mechanism that let the user specify dependencies for the buildSrc without providing a complete gradlefile Created: 17/Apr/08 Updated: 04/Jan/13 Resolved: 25/Jun/11 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 0.1 |
| Fix Version/s: | 1.0-milestone-4 |
| Type: | New Feature | ||
| Reporter: | Hans Dockter | Assignee: | Adam Murdoch |
| Resolution: | Fixed | Votes: | 0 |
| Comments |
| Comment by Jon Cox [ 23/Jan/09 ] |
|
What would you envision an incomplete gradle file looking like, |
| Comment by Hans Dockter [ 25/Jan/09 ] |
|
This is a specific buildSrc issue. If your buildSrc build does not has dependencies you don't need to provide a build script. If it does has dependencies, you need to copy and paste the default build script and modify it. This is not nice. For the common use case of having a buildSrc build with dependencies we should provide something more user friendly and maintainable. |