[
http://jira.codehaus.org/browse/MINVOKER-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165714#action_165714
]
Benjamin Bentmann commented on MINVOKER-77:
-------------------------------------------
I added some more bits to the picture to make sure the reports show up nicely
in German, too :-)
However, I am not sure whether the lifecycle forking is appropriate here. Most
ITs will require artifact staging via "install" so a "mvn clean site" will
fail. Adding "install" to the invoker-report lifecycle would require forking
the build up to "package" phase which is way too far, IMHO. Hence I believe
we're better off with not forking at all, i.e. require users to invoke "mvn
integration-test site" when they want reports after cleaning the build output.
Considering that a release typically involves "mvn clean deploy site-deploy"
not forking should fit better into the overall build. WDYT Olivier?
> Add a invoker report mojo which display invoker its result
> -----------------------------------------------------------
>
> Key: MINVOKER-77
> URL: http://jira.codehaus.org/browse/MINVOKER-77
> Project: Maven 2.x Invoker Plugin
> Issue Type: New Feature
> Reporter: Olivier Lamy
> Assignee: Olivier Lamy
> Fix For: 1.4
>
>
> The result will displayed by parsing the result generated with new feature
> from MINVOKER-76
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
