Thank you Jörg, I have decided to use <executions> mechanism, but there is another problems :) How can I use the same classloader during few <executions> phases (surefire)? I have experimented with <forkMode> and other tags, but maven-surefire-plugin 2.3 is still use different classloaders.
Jörg Schaible wrote: > > vetalok wrote on Friday, July 20, 2007 2:49 PM: > >> It seems since version 2.2 maven-surefire-plugin do not care about >> order of tests: >> (3)<include>**/init/*Data*</include> >> (2)<include>**/api/*1Test.java</include> >> (1)<include>**/api/*2Test.java</include> >> How can I tell to maven to keep the order I writed? >> (<executions> mechanism is unsuitable) >> Someone can help me? > > You should not write tests that rely on a special execution sequence. No > environment running unit tests will ever assure this. > > - Jörg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/maven-surefire-plugin-2.0-and-2.3---init-phase-problem-tf4116244s177.html#a11709094 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
