[
http://jira.codehaus.org/browse/MINVOKER-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162425#action_162425
]
Benjamin Bentmann commented on MINVOKER-76:
-------------------------------------------
Just some comments on the data model suggested by Stephen's patch:
- There's a boolean attribute "failure" written out. I suggest that we allow
for an enum-like value here, say "result" which could take the values
"failure-pre-hook", "failure-build", "failure-post-hook", "success" and "skip"
(could be a future extension) for more precise diagnostic.
- In case of a failure, the report should be capable to record a failure
message (i.e. exception message or build exit code).
If I can join the party in time, I will try to introduce some simple bean to
hold/collect the data/state of a project instead of passing its path, duration,
error etc. around as individual variables. This refactoring should help to
avoid those util methods like {{isSetupProject()}}.
> Have invoker:run generate report files to allow reporting on the results of
> running invoker
> -------------------------------------------------------------------------------------------
>
> Key: MINVOKER-76
> URL: http://jira.codehaus.org/browse/MINVOKER-76
> Project: Maven 2.x Invoker Plugin
> Issue Type: Improvement
> Reporter: Stephen Connolly
> Assignee: Olivier Lamy
> Fix For: 1.4
>
> Attachments: patch.diff
>
>
> The attached patch will adds generation of basic XML reports for each invoker
> run. This will allow other tools to report on the trends and the number of
> successes / failures. If this patch gets picked up I'll have a Hudson plugin
> to read these reports and I can also write a Maven reporting plugin to
> integrate with site.
--
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
