Peter, the dot notation I was using (in fact the contents of the relevant files), as well as the location and error message, were in the original email. To summarize the rest of the thread, for whatever reason it would work when the gradle.properties file is in the project dir but not in ~/.gradle, and would then work even in ~/.gradle when the dots were removed.
For giggles, in case there was some sort of difference between the colon and equals forms of specifying things in a properties file, I tried the alternative syntax (equals) and it gives the same error. So it looks like the difference in reading from ~/.gradle/gradle.properties is that: a) nothing's logged (even at DEBUG) b) hierarchical properties aren't supported -Jim Moore On Mon, May 9, 2011 at 9:15 AM, Peter Niederwieser <[email protected]>wrote: > > Jim Moore wrote: > > > > 2) Why doesn't the dot notation work from that file but does from the > > other locations? > > > > Could you be more specific? Which exact notation does (not) work from which > location? Do you adhere to standard Java properties file notation? Here is > an example: > > foo.bar.baz=some value > > -- > Peter Niederwieser > Developer, Gradle > http://www.gradle.org > Trainer & Consultant, Gradleware > http://www.gradleware.com > Creator, Spock Framework > http://spockframework.org > > > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/gradle-gradle-properties-not-being-read-tp4372872p4381824.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 > > >
