On May 2, 2008, at 4:28 PM, Peter Niederwieser wrote:



hdockter wrote:

I see two other options right now:
One is using an customized internal groovy jar which does not include
groovyc. I don't like this solution too much.


And I'm afraid it won't really solve the problem. As long as an Ant task might see ANY class from Gradle's internal Groovy jar, we're in danger.

right



hdockter wrote:

 The other is using an
embedded script which calls groovyc and which has the user provided
groovy in its classpath. Can you think of another way of implementing
this?


I don't know how you integrate with Ant, but isn't it possible to completely
seal off Ant tasks by means of a separate classloader?

I've worked on this more than a day. One thing is that the custom classloaders you define by yourself are always wrapped in an AntClassloader. And it looks as if the custom classloaders you pass with loaderref to a taskdef are not used in a dynamic way. I succeed in the way that groovyc-1.6 was used for compiling. But then I got classcast exceptions due to incompatible versions of groovy classes. This is no fun.

I'm using a different approach now which works. I have to update the user's guide. This evening to tomorrow there will be a 0.1.4 release containing the new functionality.

I would like to use your detector for an integration test. This integration test would be a multi-project build where detector would be build in one project and the test groovy project would depend on this. Is it possible for you to send the sources of the detector? Would you put them under Apache v2?



hdockter wrote:

And finally, what about using a different version of groovy for your
actual build scripts.


I'd expect build scripts to be compatible with the Groovy version used
internally by Gradle. Otherwise things might get too complicated.

As we think about offering additional languages to Groovy for the build scripts we anyway need a very strong decoupling. Anyway, this is not on the agenda right now.

- Hans


Cheers,
Peter

--
View this message in context: http://www.nabble.com/Building-Groovy- projects-with-Gradle-tp16926886p17020622.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




Reply via email to