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. 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? 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. 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
