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?
vetalok wrote: > > Hello experts! > My tests passed ok with maven-surefire-plugin 2.0 > *********************************** > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > MyInitializationTest > *********************************** > With maven-surefire-plugin 2.3 I have another behavior: > *********************************** > MyInitializationTest > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > *********************************** > That is why I have many problems. > Why MyInitializationTest executes before "T E S T S" with 2.3 plugin > version? > How can I configure this plugin to have the behaviour I showed above > (MyInitializationTest must be executed after "T E S T S")? > Thanks. > -- View this message in context: http://www.nabble.com/maven-surefire-plugin-2.0-and-2.3---init-phase-problem-tf4116244s177.html#a11707502 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
