Luke Stephens wrote:
>
> First off the errors kicked out suck!
>
Gradle is based on a general-purpose programming language (Groovy), which
involves some tradeoffs. However, we are working on improving error
messages.
Luke Stephens wrote:
>
> Second, why is that not a valid classpath when that is taken directly from
> the user guide and I have a "libs" directory??
>
Please show where you have this from. And why do you add the libs to the
build script class path (a very advanced concept)? If the libs are used from
your code, you should add them as compile or runtime dependencies:
dependencies {
compile files("libs")
}
Luke Stephens wrote:
>
> Secondly, how do I find out what all the paths are when I am using the
> java plugin. For instance the java plugin docs mention "buildDir" but
> don't ever define it properly. How do I set the buildDir if it is not what
> I want?
>
http://www.gradle.org/current/docs/dsl/org.gradle.api.Project.html#org.gradle.api.Project:buildDir
To set it to something different:
buildDir = "foo"
Luke Stephens wrote:
>
> I like the concepts and capabilities of gradle, but I am finding the docs
> are misleading, or don't give you clear information...
>
It seems you are looking in the wrong place(s). The user guide is for
general information; the DSL guide is for the API. In any case, if you
switch to a new build system, you should be ready to invest some time to
learn it.
--
Peter Niederwieser
Principal Engineer, Gradleware
http://gradleware.com
Creator, Spock Framework
http://spockframework.org
Twitter: @pniederw
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Relative-Paths-In-build-gradle-tp4658960p4659084.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
