Hi Russel,
On Nov 3, 2008, at 10:26 AM, Russel Winder wrote:
Hans,
On Mon, 2008-11-03 at 07:13 +0100, Hans Dockter wrote:
Is there a reason why we should not use fork equals true as a default
for compile? It provides definitely a better experience regarding
classpath issues.
I would have thought fork=true was nigh on mandatory for all runs of
javac, groovyc and junit to ensure the classpath is clean and not
polluted with Ant gubbins?
My first approach was to stick with the Ant defaults. Then I adapted
them to our needs when problems arose. Javac seems capable of
isolating itself properly when run in non fork mode (if
includeAntRuntime is set to false). Groovyc can't do this as I have
just discovered (I guess you have noticed my postings to the Groovy
list). So fork = true is a must have for Groovyc compile. I can't see
any reasons why we shouldn't do the same for javac but I wanted to
ask if other people have a reason not to do it.
Another advantage of forking is that the build can define the memory
it needs and people don't have to manually modify the JAVA_OPTS.
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
