[
https://issues.apache.org/jira/browse/MNG-7479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536582#comment-17536582
]
ASF GitHub Bot commented on MNG-7479:
-------------------------------------
cstamas commented on PR #740:
URL: https://github.com/apache/maven/pull/740#issuecomment-1125964659
EventSpy is not part of plugin API and is hidden for good reasons, it is for
maven extensions as Javadoc of EventSpy nicely explains. Event spy emits Maven
Core events (about processing the build, among them mojos as well) to some
external listener extension.
For profiling please look into these
* https://github.com/takari/maven-profiler
* https://github.com/jcgay/maven-profiler
If you want to "benchmark" Mojo internals, why do you need event spy at all?
Event spy is not at all meant for this.
-1
> Export the package org.apache.maven.eventspy
> --------------------------------------------
>
> Key: MNG-7479
> URL: https://issues.apache.org/jira/browse/MNG-7479
> Project: Maven
> Issue Type: Improvement
> Components: Core
> Affects Versions: 3.8.5
> Reporter: Christoph Läubrich
> Priority: Major
>
> I'm currently try to fetch a specific EventSpy to inject an event there
> (maven-profiler).
> Sadly in my maven plugin when I try to get it injected:
> @Requirement(role = EventSpy.class, hint = "profiler", optional = true)
> EventSpy eventSpy;
> This results in ClassNotFoundException: org.apache.maven.eventspy.EventSpy
> I noticed that the maven-core do not export the 'org.apache.maven.eventspy'
> package and that is the cause of this, I'd like to suggest to export the
> package as there seem no other standard way to interact/access event spys
> otherwise.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
