I don't think is a problem in either maven or surefire plugin.
Else the surefire is behaving differently.
It looks like now, when surefire forks the jvm, will not take all the system
properties from the parent jvm.
That's why you should pass whatever system properties you want for the
tests,
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
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
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
i was told the passing hierarchy is
System(OS)
passes to
JVM
passes to
Maven
Maven cannot populate properties up to parent JVM (so other JVM threads can use
them)
JVM cannot populate properties to System-OS space (so other system processes
can use them)
please confirm,
Martin
Please file a jira for this and use 2.1.0 as the affects version so we
can get it fixed in 2.1.1
edward eric pedersson wrote:
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
Will do once I work out how to submit issues in your Jira
2009/4/20 Brian Fox bri...@infinity.nu:
Please file a jira for this and use 2.1.0 as the affects version so we can
get it fixed in 2.1.1
edward eric pedersson wrote:
Hi
We use the command line to pass on system properties to the
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
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
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
Should just be a matter of registering a new username for yourself, then
clicking the Create Issue link in the top menu at
http://jira.codehaus.org/browse/MNG
Let me know if that doesn't work for you.
-john
edward eric pedersson wrote:
Will do once I work out how to submit issues in your
John,
I am in the same case of edward and want to enable/disable test families
while executing my maven builds.
For instance, I'll want to execute every data access tests once per day
-and not after each commits because it takes time !-
For some other tests, I'd like to execute only selenium
John,
I am in the same case of edward and want to enable/disable test families
while executing my maven builds.
For instance, I'll want to execute every data access tests once per day
-and not after each commits because it takes time !-
For some other tests, I'd like to execute only selenium
13 matches
Mail list logo
