You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2023/05/04 20:13:00 UTC

[jira] [Commented] (MSHARED-650) Fire ExecutionEvent from DefaultMavenReportExecutor

    [ https://issues.apache.org/jira/browse/MSHARED-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17719521#comment-17719521 ] 

Michael Osipov commented on MSHARED-650:
----------------------------------------

[~cstamas], can you tell us your opinion on this?

> Fire ExecutionEvent from DefaultMavenReportExecutor
> ---------------------------------------------------
>
>                 Key: MSHARED-650
>                 URL: https://issues.apache.org/jira/browse/MSHARED-650
>             Project: Maven Shared Components
>          Issue Type: New Feature
>          Components: maven-reporting-exec
>            Reporter: Matt Nelson
>            Priority: Major
>
> The event spy features added currently only support plugin mojos. When building site all the report mojos are grouped together under the site plugin and do not enable the ability to profile the site and find slow mojos. I dug through the code and it appears that the {{DefaultMavenReportExecutor}}[1] could be instrumented with the Catapult to fire events for each report mojo that the {{EventSpy}}[2] can handle.
> [1] https://github.com/apache/maven-shared/blob/maven-reporting-exec-1.3/src/main/java/org/apache/maven/reporting/exec/DefaultMavenReportExecutor.java
> [2] https://github.com/apache/maven/blob/maven-3.5.0/maven-core/src/main/java/org/apache/maven/eventspy/EventSpy.java



--
This message was sent by Atlassian Jira
(v8.20.10#820010)