FYI: This is a failsafe specific questionand I'm hoping this is the
correct fall-back mailing list as the
surefire-users-subscr...@maven.apache.org address bounces
(http://maven.apache.org/surefire/maven-failsafe-plugin/mail-lists.html).
I'm using version 2.13 of the maven failsafe plugin.
Slightly OT.
Why are you using argLine which is for things like JVM memory options
(think -Xmx512m) and not
http://maven.apache.org/surefire/maven-failsafe-plugin/integration-test-mojo.html#systemPropertyVariablesfor
setting the system properties in surefire/falsesafe's forked JVMs?
You may have
Also the it.test property is parsed by the Mojo and normally not passed
through to the surefire engine. IOW the Maven plugin uses that property to
decide what tests to ask for running.
On 5 February 2013 13:51, Stephen Connolly
stephen.alan.conno...@gmail.comwrote:
Slightly OT.
Why are you
That's a-okayto be OT. :) I appreciate the feedback.
I've updated the configuration to use systemPropertyVariables but I
still reproduce the same problem. When I supply it.case via the command
line, the properties fed into each execution via the
systempropertyvalues block are nullified.
Yea, I was going to start by debugging the Mojo to see what happens with
the properties.
I'll peek around some more and may end up in the issue tracker.
Thanks for your help,
Tim
On 05/02/2013 9:52 AM, Stephen Connolly wrote:
Also the it.test property is parsed by the Mojo and normally not
