Well, if you want, go ahead and file a JIRA for it in
http://jira.codehaus.org/browse/MNG and we can at least take a look to
make sure there isn't a better way.
FWIW, if you put the systemProperties entry in place with a value of
'${system.property}', then use -Dsystem.property=foo in the mvn command
line, that will probably work. It's at least something to try.
-john
edward eric pedersson wrote:
I need to pass the options on the command line so using
systemProperties might not work for me unless I misunderstand what you
mean.
How do you pass the -DpropertyName using the MAVEN_OPTS ? I m pretty
sure that was the first thing I tried before adding them as system
properties properly as described in my email earlier.
I did search for documentation but it was kind of sparse.
2009/4/20 John Casey <jdca...@commonjava.org>:
Another couple things to consider:
1. in Surefire, you should probably use the systemProperties to pass on
system properties explicitly. Just a suggestion.
2. For actual system properties, it might be wiser to set them in MAVEN_OPTS
instead of the mvn -D option. This is because Maven has deprecated the
propagation of -D options into system properties, in order to make it a
little friendlier for people trying to run multiple maven instances in a
single JVM (without getting cross-pollution of sysprops).
Using MAVEN_OPTS (which IIRC you can set in Hudson), you can still specify
'-Dsystem.property=foo' and have it work fine.
-john
edward eric pedersson wrote:
yes you are right.
It seems 2.4.3 of the plugin is broken but 2.4.2 works just fine.
will lock down the version is the pom.
thanks for your help
2009/4/20 Stephen Connolly <stephen.alan.conno...@gmail.com>:
Have you locked down the version of surefire you are using in your pom?
if you have not locked it down, then you will be picking up a newer
version of surefire with 2.1.0.
AFAIK, a newer version of surefire has issues passing system
properties to the forked process.
in any case you should always lock down the versions of plugins that
you are using or else your build is not fully reproducible
-Stephen
2009/4/20 edward eric pedersson <cpsmadn...@googlemail.com>:
Hi
We use the command line to pass on system properties to the java
virtual machine when running our Hudson builds on a Linux box. It used
to work quite well in 2.0.9 by since we upgraded to 2.1.0 it has
stopped working altogether. The system properties just never make it
to the java virtual machine.
I have created a small test project and indeed it does not work at
all. I have attached it in case you want to give it a go. [it got
blocked so sending without attachment]
This should work just fine with maven 2.0.9
mvn2.0.9 -Dsystem.test.property=test test
But this will fail
mvn2.1 -Dsystem.test.property=test test
The java code simply does this
assertTrue( System.getProperty("system.test.property") != null);
Any thoughts
--
-- e
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
