Russel Winder wrote:
I am fairly sure the gradle jar is in the class path when I instantiate
GradleLauncher yet I am getting and exception whose failure object
reports:
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup
failed, init_gradle_2138bc63226bfc977e60d0900852cd98: 1: unable to
resolve class org.gradle.initialization.InitScript
So it seems that the classpath gets changed somewhere along the line.
Which is sort of reasonable and yet not reasonable.
Are there any good, working examples of using GradleLauncher anywhere?
The integration tests use it to run Gradle builds. See
InProcessGradleExecuter, for example.
I have a feeling you also need to set the 'gradle.home' system property
for things to work, as there's some code which does not use
StartParameters.gradleHomeDir to find Jars.
Embedding Gradle is still in a pretty crap state. Too many things assume
the build has been launched by BootstrapMain. Hopefully this will get a
revamp in the 0.9 release.
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
