[GRADLE-183] Dependency Layer Refactoring Created: 20/Aug/08 Updated: 04/Jan/13 Resolved: 07/Apr/09
|Reporter:||Hans Dockter||Assignee:||Hans Dockter|
As discussed in: http://www.nabble.com/dependency-layer-refactoring-to18725442.html
|Comment by Jon Cox [ 22/Jan/09 ]|
I had to re-read the docs several times before I finally got what was going on here (more or less).
Gradle dependencies are grouped into "dependency configurations".
Many of these dependency configurations have the same name as the task they're typically linked to,
By default, Gradle gives you the following set of "dependency configurations":
For example, the 'compile' configuration comes already linked to the 'compile' task,
Some of the pre-built dependency configurations provided by the Java (or Groovy)
|Comment by Hans Dockter [ 25/Jan/09 ]|
How Gradle 0.5 links tasks with configurations is ugly and unintuitive. In my working copy there is now a much nicer and more powerful mechanism (as discussed on the mailing list recently). I hope to submit this within the next days.