Re: How to find out which parameters can be specified as command-line properties?

2010-03-13 Thread Paul Benedict
Yup, and you can use an abbreviated version too: mvn help:describe -Dplugin=surefire -Ddetail=true On Sat, Mar 13, 2010 at 2:30 PM, Mirko Friedenhagen wrote: > Am 13.03.2010 um 03:06 schrieb sebb: >> Some plugin parameters are settable as command-line properties. >> For example, the Surefire plug

Re: How to find out which parameters can be specified as command-line properties?

2010-03-13 Thread Mirko Friedenhagen
Am 13.03.2010 um 03:06 schrieb sebb: > Some plugin parameters are settable as command-line properties. > For example, the Surefire plugin accepts the parameter in > the POM and the property -DargLine on the command-line. > > Surefire also accepts and -DskipTests=true. > > However, Surefire acce

Re: How to find out which parameters can be specified as command-line properties?

2010-03-12 Thread Anders Hammar
Look for "Expression" in the docs. For example, the surefire:test skip param: http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#skip /Anders On Sat, Mar 13, 2010 at 03:06, sebb wrote: > Some plugin parameters are settable as command-line properties. > For example, the Surefir

How to find out which parameters can be specified as command-line properties?

2010-03-12 Thread sebb
Some plugin parameters are settable as command-line properties. For example, the Surefire plugin accepts the parameter in the POM and the property -DargLine on the command-line. Surefire also accepts and -DskipTests=true. However, Surefire accepts the parameter, but ignores -Dskip=true. How c