[ https://jira.codehaus.org/browse/MNG-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346142#comment-346142 ]
Herve Boutemy commented on MNG-5630: ------------------------------------ I understand your point I'm convincend this information on what *is* forked is even more useful at INFO level that what *has* forked perhaps we can remove the mojoExecutionId (ie "(report:aggregate)" in the example) since it will be displayed when running the mojo? > 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)