Yuri Bendana wrote:
>
> I noticed that buildscript.dependencies() is different from dependencies()
> because in the first only the 'classpath' configuration exists while in
> the second, the classpath configuration no longer exists. The User Guide
> didn't make this point obvious, why are there two different ways of
> setting the classpath?
>
The dependencies {} section contains the dependencies needed to build (i.e.
compile, test, etc.) the project. By default, it doesn't have a
configuration named 'classpath' (but rather 'compile', 'runtime', etc.).
The buildscript {} section is very special. It gets evaluated before the
rest of the build script, and contains vital information necessary for
evaluating the build script. Among other things, it allows you to declare
dependencies used by the build script itself. That's what the 'classpath'
configuration is about. It is only needed for advanced builds.
--
Peter Niederwieser
Developer, Gradle
http://www.gradle.org
Trainer & Consultant, Gradle Inc.
http://www.gradle.biz
Creator, Spock Framework
http://spockframework.org
--
View this message in context:
http://gradle.1045684.n5.nabble.com/classpath-issue-resolved-tp3385429p3386586.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
