Kenneth Kousen wrote:
>
>> Even better, introduce your own configuration (e.g. 'script') and use
>> that.
>
> Um, how do I do that? Can you point me to an example?
>
configurations {
script
}
dependencies {
script ...
}
But if the script also needs the current project's code, the solution posted
by Adam is best.
If I understand the JavaExec tasks, I need to know the compiled class name.
What's that for a script? (I might be able to figure that one out. :)
< /quote>
The class name is the script's filename.
--
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/Run-groovy-script-from-gradle-with-classpath-tp4664822p4672479.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
