[
https://jira.codehaus.org/browse/MNG-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346211#comment-346211
]
Paul Benedict commented on MNG-5630:
------------------------------------
The output looks good. However, I am inclined to say that there should be a
option/parameter (or logging category) to turn on this level of forking detail.
It's awfully a lot of detail for the default display.
> improve display of forked executions
> ------------------------------------
>
> Key: MNG-5630
> URL: https://jira.codehaus.org/browse/MNG-5630
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Command Line
> Affects Versions: 3.2.1
> Reporter: Herve Boutemy
> Assignee: Herve Boutemy
> Fix For: 3.2.2
>
> Attachments: mvn-Preporting-site.log.zip
>
>
> Currently we have
> {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 doesn't tell what is the forked goal or phase, which would be useful
> proposed new format in case of phase:
> {noformat}[INFO]
> [INFO] >>> maven-javadoc-plugin:2.9.1:aggregate (report:aggregate) >
> [optional lifecycle]generate-sources @ forked-lifecycle >>>
> [INFO]
> [INFO] <<< maven-javadoc-plugin:2.9.1:aggregate (report:aggregate) <
> [optional lifecycle]generate-sources @ forked-lifecycle <<<{noformat}
> and in case of goal:
> proposed new format in case of phase:
> {noformat}[INFO]
> [INFO] >>> maven-javadoc-plugin:2.9.1:aggregate (report:aggregate) > :goal @
> forked-lifecycle >>>
> [INFO]
> [INFO] <<< maven-javadoc-plugin:2.9.1:aggregate (report:aggregate) < :goal @
> forked-lifecycle <<<{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
