On Sep 16, 2009, at 8:15 PM, Steve Appling wrote:
Hans Dockter wrote:
On Sep 16, 2009, at 2:02 PM, Steve Appling wrote:
Using the depend option actually helps with many of these kinds of
problems now:
compile.options.depend()
I have almost forgotten about that. We discussed it in our last dev
skype conference whether to make it default or not. I argued not to
make it default but I was very tired then. On the next my arguments
didn't make sense to me but I forgot to pick it up again.
As far as I can tell the only reason not to make it default would
be, if it actually increases the compile time for smaller projects.
Gradle's own build just doesn't use it.
I'm all for changing this or to make it default.
- Hans
Actually I think I'll have to retract my previous assertion. The
depend option is only useful for java compiles, not for groovy
compiles. It is only implemented in AntJavac because the ant depend
task only works with Java sources :( If you did change AntGroovyc
to try to use this task, it would force deletion of all classes
generated from Groovy sources each time - not what you want.
I don't think this will be helpful for mixed Java/Groovy source trees.
The gradle-ui project could probably use this since (in spite of
being under src/main/groovy) it currently only uses java sources (it
has some groovy tests).
The gradle-core project, however, is a truly mixed source project.
Right. Should we set it as the default for Java projects?
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
