On May 8, 2008, at 7:06 AM, Allan Lewis wrote:
Hi Hans,
I still need to come up with a good test case, but in the meantime,
here is
some more info. I run into issues if I try to execute code from the
'generatefile' you came up with for my multi-project build
(executed from a
compile.doFirst block). However, this same code works perfectly
well if run
from a JUnit test. Can you think of anything offhand that would be
different in these 2 cases?
I guess it has something to do with:
new GroovyShell(new URLClassLoader(classpath, Thread.currentThread
().contextClassLoader),
new Binding(project: project)).evaluate(file
('generatefile'))
This could lead to classloading problems. What kind of Exceptions did
you get?
- Hans
I remember that when I worked with Maven
plugins that I had to force the dependency resolution for my plugin to
'test' to get things to run correctly during the 'generate-sources'
phase...
Thanks
Allan
--
View this message in context: http://www.nabble.com/Classpaths-
classloaders-in-Gradle-tp17105685p17120154.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