On Mon, Dec 14, 2009 at 4:34 PM, Hans Dockter <[email protected]> wrote:
> > > On Mon, Dec 14, 2009 at 12:00 PM, Roshan Dawrani < > [email protected]> wrote: > >> Hi Hans, >> I had tried GRADLE_OPTS and that does not work on the forked java process >> that <groovyc> launches. >> >> I did not try to "not fork" because then I was not sure whether I will be >> getting gradle's classloader isolation or not. >> > > The Gradle classloader isolation should work also in non forked mode. It > would be a bug if not. > > Ok, I will go ahead based on that then. Could you please point me into gradle codebase where it uses <groovyc> and launches the groovy compilation based on the dependencies of the project it is doing the build in? If using fork=false does not work out, I would like to look in that area before raising it here again? Some pointers to where I should look will be helpful. Thanks for your help. > - Hans > > -- > Hans Dockter > Gradle Project Manager > http://www.gradle.org > >
