I don't quite understand what you mean. You're saying that if the
environment you run your tests in uses those variables, and we run
integration tests that fork Maven, they aren't passed on by default?
It's a bit ugly - it'd be nicer if the test framework took care of
that, but I can see what you mean and it might make sense to add them
in to the parent.
- Brett
On 06/03/2008, at 3:30 AM, Arnaud HERITIER wrote:
Hi guys,
To fix an issue (MECLIPSE-395) to build the eclipse plugin with a
fully
customized environment, I had to add in surefire these settings :
<systemProperties>
<property>
<name>maven.home</name>
<value>${maven.home}</value>
</property>
<property>
<name>org.apache.maven.user-settings</name>
<value>${org.apache.maven.user-settings}</value>
</property>
<property>
<name>org.apache.maven.global-settings</name>
<value>${org.apache.maven.global-settings}</value>
</property>
</systemProperties>
I reproduced this issue in others plugins and librairies like the
maven-plugin-testing-tools.
Couldn't we add these settings in a parent pom ? Which one ? The
maven-plugins parent seems a good location ?
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
