I just noticed that my fix doesn't work if those properties aren't defined
(see my comment o*n MECLIPSE-395*).
I don't see how to fix this problem. It's no something that is annoying a
lot of people (that's why I'm the first one t notice it) but if someone can
help me to fix it or to find a
On Wed, Mar 5, 2008 at 9:13 PM, Brett Porter [EMAIL PROTECTED] wrote:
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?
yes, exactly.
Yes, I suppose that we are few to use those properties (I never used them
before yesterday) but I agree it should be transparent for plugins
developments and integration tests. I'll try to find a fix in
maven-plugin-testing-tools.
Arnaud
On Wed, Mar 5, 2008 at 9:34 PM, Jason van Zyl [EMAIL
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
namemaven.home/name
value${maven.home}/value
/property
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
I doubt we need these for many of the plugins, and the invoker or
SHITTY plugin should deal with. I'd rather not see this foisted on
everyone.
On 5-Mar-08, at 8:30 AM, Arnaud HERITIER wrote:
Hi guys,
To fix an issue (MECLIPSE-395) to build the eclipse plugin with a
fully
customized
