[
https://jira.codehaus.org/browse/MSHARED-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346025#comment-346025
]
Herve Boutemy commented on MSHARED-333:
---------------------------------------
done in [r1593705|http://svn.apache.org/r1593705]
result is
{noformat}[INFO] aggregate report requires generate-sources forked phase
execution
[INFO]
[INFO] >>> maven-javadoc-plugin:2.9.1:aggregate (report:aggregate) @
forked-lifecycle >>>
...
[INFO]
[INFO] <<< maven-javadoc-plugin:2.9.1:aggregate (report:aggregate) @
forked-lifecycle <<<{noformat}
> display what phase or goal is forked by a report
> ------------------------------------------------
>
> Key: MSHARED-333
> URL: https://jira.codehaus.org/browse/MSHARED-333
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-reporting-exec
> Reporter: Herve Boutemy
> Fix For: maven-reporting-exec-1.1.1
>
>
> actually, forked executions don't show what is the precise phase or goal that
> is forked
> {noformat}[INFO]
> [INFO] >>> maven-javadoc-plugin:2.9.1:aggregate (report:aggregate) @
> forked-lifecycle >>>
> ...
> [INFO]
> [INFO] <<< maven-javadoc-plugin:2.9.1:aggregate (report:aggregate) @
> forked-lifecycle <<<{noformat}
> it would be useful to know what is the phase or goal that cause the forked
> execution
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
