We do it like this:
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<forkMode>once</forkMode>
<workingDirectory>target</workingDirectory>
<argLine>-Djava.library.path=lib</argLine>
On Wed, Sep 24, 2008 at 10:17 AM, leojhartiv <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I searched the archive, but was not able to find an answer to my question.
>
> I am running maven as follows:
>
> mvn clean test -Dsomeparameter=somevalue
>
> someparameter will vary per mvn call.
>
> It does not appear that my surefire tests are able to find this variable
> when they execute, so I'm assuming Maven does not pass all command-line
> variables to plugins by default.
>
> My question is, how do I pass surefire a command-line argument? My first
> thought was to do so in the configuration:
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-surefire-plugin</artifactId>
> <version>2.4.3</version>
> <configuration>
> <systemProperties>
> <property>
> <name>someparameter</name>
> <value>${someparameter}</value>
> </property>
> </systemProperties>
> </configuration>
> </plugin>
>
> However, looking at this page, it seems that this will not work:
>
>
> http://maven.apache.org/plugins/maven-surefire-plugin/examples/system-properties.html
>
> Any solution you have is appreciated.
>
> Thanks,
> Leo
> --
> View this message in context:
> http://www.nabble.com/Pass-Command-Line-Param-to-Surefire-Plugin-tp19653694p19653694.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
