On Thu, 2009-09-03 at 15:01 +1000, Adam Murdoch wrote: [ . . . ] > The integration tests use it to run Gradle builds. See > InProcessGradleExecuter, for example.
OK thanks, I'll take a look.
> 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.
My context is creating a class to realize the <gradle> tag for Ant. I
should be able to deduce a Gradle home since Ant must have the gradle
jar in its classpath in order to instantiate the class I am writing.
The only question is how to find this information using the ant API.
If I have to set gradle.home as well as calling setGradleHomeDir, then I
think there is an API problem that needs fixing.
> 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.
OK, I'll take this as a green light to moan about all the hassles I see.
Oh, I already do that ;-)
So far the basic structure of StartParameter and GradleLauncher seems
entirely fine. The main irritation is having to convert from the
objects used by Ant to build the task information to the strings
required by the GradleLauncher API. But this is not really a big deal.
--
Russel.
=============================================================================
Dr Russel Winder Partner
xmpp: [email protected]
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip: sip:[email protected]
London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder
signature.asc
Description: This is a digitally signed message part
