It's something that's planned but isn't a priority, partly because it isn't easy to implement it well. Today, the best solution is the one I've shown in my previous email. If you just need to configure a couple of properties from the command line, this solution is good enough. If necessary, you could try to come up with a more general solution, for example based on reflection.
In general, the need for configuring many different properties from the command line should be considered a smell. It makes the build less repeatable, less convenient and more error prone. Gradle's philosophy is to keep as much information as possible in its model and under source control. In case of the test categories, an alternative to passing command line args is to declare multiple test tasks (possibly dynamically in a loop or with Gradle's task rule feature), each of which runs a different set of tests. As of Spock 0.6, you can't configure categories via system properties alone; you additionally need a spock configuration file. Starting with 0.7, a system property will suffice. -- Peter Niederwieser Principal Engineer, Gradleware http://gradleware.com Creator, Spock Framework http://spockframework.org Twitter: @pniederw -- View this message in context: http://gradle.1045684.n5.nabble.com/passing-jvm-args-to-forked-jvm-tp5580908p5584253.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
