[ 
https://jira.codehaus.org/browse/MNG-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346358#comment-346358
 ] 

Herve Boutemy commented on MNG-5630:
------------------------------------

remember that the commit was just addition of "> generate-sources": your 
remarks about report:javadoc are just about discovering something that existed 
before (and to be honest, I discovered it too :) )
first, we need to [have a look at the 
javadoc|http://maven.apache.org/ref/3-LATEST/maven-embedder/apidocs/org/apache/maven/cli/event/ExecutionEventLogger.html#forkStarted(org.apache.maven.execution.ExecutionEvent)]:
 report:javadoc is the mojo-executionId
it is calculated in 
[DefaultMavenReportExecutor|http://maven.apache.org/shared/maven-reporting-exec/xref/org/apache/maven/reporting/exec/DefaultMavenReportExecutor.html#239]

I don't really know how it is used

then the surefire lifecycle is in the report goal configuration: see [the 
documentation|http://maven.apache.org/surefire/maven-surefire-report-plugin/report-mojo.html]
once again, I don't really know how it is used


the examples just permit you to discover things we didn't even remark before, 
but that was running: this could help us understand some problems we encounter 
with m-site-p

> 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)

Reply via email to