maven 2.0.10 uses surefire 2.4.3 which will break your test scenario, you need to pin down your sure fire to 2.4.2
and i think 2.0.9 uses 2.4.2 -D On Wed, Mar 18, 2009 at 3:52 PM, Stefano Fornari <[email protected]> wrote: > Sorry, I am not sure the zip went through. Here are the relevant classes... > > On Wed, Mar 18, 2009 at 11:48 PM, Stefano Fornari > <[email protected]> wrote: >> Hi All, >> Has anyone experiencing the same problem? Up to maven 2.0.9 I was used >> to test the project with a command line similar to: >> >> mvn -D__TEST__=true test >> >> The test code uses System.getProperty("__TEST__") and gets the value >> passed on the command line. With maven 2.0.10 this doe snot happen, so >> the tests do not pass because of the missing property. Is this the >> intended behaviour? Or is it a bug? I am attaching a test project if >> anyone is kind to spend some time to try it out. >> >> Thanks in advance. >> >> >> -- >> Ste >> > > > > -- > Ste > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
