Re: [jboss-as7-dev] Testsuite grouping: Splitting to many modules, or something different?

Hi Jason. Use reportNameSuffix [1] for surefire configuration in your module or execution. General solution would be to define empty property<surefire.default.reportNameSuffix /> and add<reportNameSuffix>${surefire.default.reportNameSuffix}</reportNameSuffix> into maven-surefire-plugin configuration in testsuite/pom.xml. In your module or execution you can just redefine the property. There is no filename change when reportNameSuffix is null or empty. Cheers. Rosta [1] http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#repo... ----- Original Message ----- > On 12/2/11 10:22 AM, Jason T. Greene wrote: >> On 12/2/11 10:20 AM, Brian Stansberry wrote: >>> On 12/2/11 10:15 AM, Jason T. Greene wrote: > >>>> Also note, that I'm not arguing for 20 modules right now. What I >>>> am >>>> saying is that we can take the 3 or so that require full and make >>>> them >>>> modules right now, and then later, over time migrate when needed. >>>> >>> >>> I argued in a separate message against significant refactors prior >>> to >>> CR1. I don't regard what you're described in this last paragraph >>> as a >>> significant refactor. >>> >> >> BTW I should note that I can live with the two execution status >> quo. >> It's not great but it does work (mostly). >> > > Another problem I just discovered with multiple executions, is that > hudson test results using the maven plugin are masked. So we really > should move off of this at our earliest convenience. > > -- > Jason T. Greene > JBoss AS Lead / EAP Platform Architect > JBoss, a division of Red Hat > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >