Not that I am aware of. Plus, to the best of my knowledge the plan is to actually remove settings.gradle[1]. There are plans to make properties even more slick[2][3].
[1] http://jira.codehaus.org/browse/GRADLE-338 [2] http://jira.codehaus.org/browse/GRADLE-699 [3] http://jira.codehaus.org/browse/GRADLE-700 On Mon, 2010-07-26 at 14:32 +0200, Levi Hoogenberg wrote: > Good afternoon, > > is it possible to check for the presence of a property in > settings.gradle without resorting to a try/catch block? > > Background: I'd like to provide a way for users to include certain > subprojects in the build. My first thought was to use > gradle.properties. Trying to use a property that's defined in > gradle.properties works (so far so good), but if the user does not > have a gradle.properties file (e.g. in the initial situation), Gradle > throws an exception. I've been looking around the sources and > documentation (Settings/ProjectDescriptor/StartParameter), but can't > find a method that's equivalent to Project's hasProperty method. So > I'm using a try/catch block at the moment. > > Thanks in advance, > Levi -- Steve Ebersole <[email protected]> http://hibernate.org --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
