On Thu, 2009-09-03 at 14:56 +1000, Adam Murdoch wrote: [ . . . ] > You're seeing a symptom here, rather than the cause. You don't have to > set the plugin properties file. You do, however, have to set the > StartParameters.gradleHomeDir property. When you don't, you get the > above misleading error message. Of course, it would be much better if > you got an error message telling you to set the Gradle home dir. Or if > you didn't have to set it at all and Gradle just figured it out.
OK so I guess there needs to be a JIRA saying forgetting to
setGradleHomeDir causes spurious NPE relating to pluginPropertiesFile.
Now the really core question: how is a bit of code to know where Gradle
is stored. Does this mean it is mandatory for there to be a GRADLE_HOME
environment variable? If so then why can't this be the default in each
instance of StartParameters. Alternatively there should be a mechanism
to deduce the home given the location of the Gradle jar being used, then
this could be the default value.
All in all, I currently believe that it should be handled by default and
there should not be a need to explicitly set this value.
In my specific case (an Ant task to initiate Gradle), the Gradle home
that is known to Ant in order to instantiate the class implementing the
gradle task must be findable. This is an Ant API problem though. I
guess I just have to hunt.
--
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
