In Gradle we have the necessity that some information is provided
_before_ the build script is compiled (for example if you want to add
additional jars to the build script classpath). At the moment we solve
this with a settings.gradle file. Tom and I have talked about this
during Devoxx. We both would love to get rid of this additional build
file 'settings.gradle'. What we would like to do instead, is to have a
two phase processing of the build.gradle file. The first parsing would
extract information for example about the build script classpath or
about project naming. The second step would be the actual compile.
To implement the first phase, we could either use some home made
regular expression stuff. Or we could use some off the hidden Groovy
1.6 compile magic (Peter Niederwieser would need to help us out here).
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
