On Jun 4, 2008, at 6:14 PM, JerodLass wrote:
I have a groovy method that I use in my gradlefile to add a bunch
of .jars to
the unmanagedClasspath. Is there a way for the top-level project
to call it
to add these .jars (which are needed by more or less every
subproject) to
the classpaths of all subprojects? This would allow me to cut the
number of
lines of every subproject's gradlefile almost in half. If I just
call it
from the top-level gradlefile, the subprojects have trouble finding
the
.jars. Thanks.
As much as I would like to find out whether this is a Gradle bug or
not. Why not using normal dependencies instead of the unmanaged ones?
- Hans
-Jerod
--
View this message in context: http://www.nabble.com/gradlefile-
cleaning--tp17650512p17650512.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
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
