Hi Dan, looking at the bug, it still does not answer (or at least I did not get it) if this is a bug or the wanted behaviour.
The given workaround does not work for me because I cannot put values in the pom. Ste On Thu, Mar 19, 2009 at 2:16 AM, Dan Tran <[email protected]> wrote: > see this issue for details > > https://jira.codehaus.org/browse/SUREFIRE-121 > > -D > > On Wed, Mar 18, 2009 at 4:25 PM, Stefano Fornari > <[email protected]> wrote: >> Hi Dan, >> thanks fo the quick reply. But do you mean that this is the correct >> behaviour of surefire 2.4.3? It seems odd to me. >> >> Ste >> >> >> >> On Thu, Mar 19, 2009 at 12:07 AM, Dan Tran <[email protected]> wrote: >>> 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 >>> -- Ste --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
