[
https://issues.jboss.org/browse/AS7-2011?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka commented on AS7-2011:
-----------------------------------
{quote}
I can't get maven modules run in desired order.
I have ported test-reporting for the testsuite.
Now I am trying to put it to right place in POM.
Ideally, `mvn install site` should have reporting by default, `-DnoReport` should skip
reporting.
I've tried:
1) Having in testsuite/pom.xml, bound to the site phase.
This needs to run `mvn site` in a separate command, like `mvn install; mvn site`, since
with `mvn install site` reporting would run before the submodules (with tests) were run.
2) Having it in testsuite/reporting/pom.xml
Because of how testsuite/pom.xml is written (multiple profiles activating modules used to
separate certain test groups),
reporting must be defined in a profile, in order to run it after other submodules.
That blocks having it auto-activated since it's not possible to move auto-activated
profiles after property-activated.
So it's only possible to having it not running by default, and running on-demand.
(And that's what I am going to use as fallback solution.)
Any idea how should I get this working "ideally", as defined above?
{quote}
TS: Implement test reporting.
-----------------------------
Key: AS7-2011
URL:
https://issues.jboss.org/browse/AS7-2011
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Reporter: Ondrej Zizka
Assignee: Ondrej Zizka
Attachments: JUnitDiff-two-runs-comparison.html
Make sure test reports are being produced correctly (this may involve
chasing up Paul Gier for the surefire release).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira