Doh, nm, didn't see the profiles were activated by a property. itblast has to do some rather unseemly stuff to get Cargo to run twice, once for startup and once for shutdown. It is possible itblast doesn't completely clear out state on shutdown. I'd recommend running mvnDebug and stepping through to see what is going on.
Don On Tue, Sep 29, 2009 at 3:22 PM, Don Brown <[email protected]> wrote: > Well, -D won't do anything, but -P will...can you try > -Prun_tests_oracle,run_tests_sqlserver? > > Don > > On Tue, Aug 4, 2009 at 6:13 PM, Nafter <[email protected]> wrote: >> >> When I make a build at the end the maven-itblast-plugin is used to kick off >> Junit tests. >> This is working just fine. >> >> However I would like to run the same set of JUnit tests against an other db >> vendor as well. >> In fact the Junit tests should be executed on a Oracle database but also on >> a SQL server database. >> >> At the moment I'm trying to invoke the maven-itblast-plugin two times, but >> this is only executed once. >> >> I call the build by passing the following profile options: >> >> -e clean install -Drun_tests_oracle -Drun_tests_sqlserver >> >> >> Does somebody know how to really invoke the Unittests twice using the >> maven-itblast-plugin? >> >> >> >> See below how the -Drun_tests_oracle -Drun_tests_sqlserver are being >> configured. >> <!-- RUN ACTUAL JUNIT TESTS [ORACLE] --> >> <profile> >> <id>run_tests_oracle_id</id> >> <activation> >> <property> >> <name>run_tests_oracle</name> >> </property> >> </activation> >> <build> >> <plugins> >> <plugin> >> <groupId>org.codehaus.cargo</groupId> >> <artifactId>cargo-maven2-plugin</artifactId> >> <version>1.0-beta-2</version> >> >> <configuration> >> <!-- Container configuration --> >> <container> >> <containerId>jboss42x</containerId> >> <home>${JBOSS__HOME}</home> >> </container> >> <!-- Configuration to use with the container --> >> <configuration> >> <type>standalone</type> >> <home>${JBOSS__HOME}/server/default</home> >> <properties> >> <!--<cargo.rmi.port>${JBOSS_PORT__RMI}</cargo.rmi.port>--> >> >> <cargo.jvmargs>${VMARGS__TEST_PROPERTY_FILE_ORACLE}</cargo.jvmargs> >> </properties> >> </configuration> >> </configuration> >> </plugin> >> >> <plugin> >> <artifactId>maven-surefire-plugin</artifactId> >> <configuration> >> <skip>false</skip> >> <argLine>${VMARGS__TEST_PROPERTY_FILE_ORACLE}</argLine> >> <testFailureIgnore>false</testFailureIgnore> >> </configuration> >> </plugin> >> >> <plugin> >> <groupId>org.twdata.maven</groupId> >> <artifactId>maven-itblast-plugin</artifactId> >> <version>0.5</version> >> <executions> >> <execution> >> <phase>verify</phase> >> <goals> >> <goal>execute</goal> >> </goals> >> <configuration> >> <containers>jboss42x</containers> >> <httpPort>${JBOSS_PORT__HTTP}</httpPort> >> <rmiPort>${JBOSS_PORT__RMI}</rmiPort> >> >> <functionalTestPattern>${JUNIT__TEST_PATTERN}</functionalTestPattern> >> <systemProperties></systemProperties> >> </configuration> >> </execution> >> </executions> >> </plugin> >> </plugins> >> </build> >> </profile> >> >> >> >> <!-- RUN ACTUAL JUNIT TESTS [SQL SERVER] --> >> <profile> >> <id>run_tests_sqlserver_id</id> >> <activation> >> <property> >> <name>run_tests_sqlserver</name> >> </property> >> </activation> >> <build> >> <plugins> >> <plugin> >> <groupId>org.codehaus.cargo</groupId> >> <artifactId>cargo-maven2-plugin</artifactId> >> <version>1.0-beta-2</version> >> >> <configuration> >> <!-- Container configuration --> >> <container> >> <containerId>jboss42x</containerId> >> <home>${JBOSS__HOME}</home> >> </container> >> <!-- Configuration to use with the container --> >> <configuration> >> <type>standalone</type> >> <home>${JBOSS__HOME}/server/default</home> >> <properties> >> <!--<cargo.rmi.port>${JBOSS_PORT__RMI}</cargo.rmi.port>--> >> >> <cargo.jvmargs>${VMARGS__TEST_PROPERTY_FILE_SQLSERVER}</cargo.jvmargs> >> </properties> >> </configuration> >> </configuration> >> </plugin> >> >> <plugin> >> <artifactId>maven-surefire-plugin</artifactId> >> <configuration> >> <skip>false</skip> >> <argLine>${VMARGS__TEST_PROPERTY_FILE_SQLSERVER}</argLine> >> <testFailureIgnore>false</testFailureIgnore> >> </configuration> >> </plugin> >> >> <plugin> >> <groupId>org.twdata.maven</groupId> >> <artifactId>maven-itblast-plugin</artifactId> >> <version>0.5</version> >> <executions> >> <execution> >> <phase>verify</phase> >> <goals> >> <goal>execute</goal> >> </goals> >> <configuration> >> <containers>jboss42x</containers> >> <httpPort>${JBOSS_PORT__HTTP}</httpPort> >> <rmiPort>${JBOSS_PORT__RMI}</rmiPort> >> >> <functionalTestPattern>${JUNIT__TEST_PATTERN}</functionalTestPattern> >> <systemProperties></systemProperties> >> </configuration> >> </execution> >> </executions> >> </plugin> >> </plugins> >> </build> >> </profile> >> >> -- >> View this message in context: >> http://www.nabble.com/How-invoke-itblast-plugin-two-times-for-two-different-databases--tp24804090p24804090.html >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> 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]
