[
https://jira.codehaus.org/browse/MNG-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346083#comment-346083
]
Michael Osipov commented on MNG-5630:
-------------------------------------
I do not like the line length it introduced now. Now we have by default a line
which is longer than 100 chars. With all the information logged out to the
shell, it will make it even more unreable but the idea is good in general.
Maybe such information should be shown in a debug execution?
> 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
>
>
> actually, 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)
