[
https://issues.apache.org/jira/browse/MNG-7479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536643#comment-17536643
]
ASF GitHub Bot commented on MNG-7479:
-------------------------------------
gnodet commented on PR #740:
URL: https://github.com/apache/maven/pull/740#issuecomment-1126052315
The event spy is the only one capable of producing actual timing for mojos.
We have brought one inspired from takari in mvnd iirc :
https://github.com/apache/maven-mvnd/blob/master/daemon/src/main/java/org/mvndaemon/mvnd/timing/BuildTimeEventSpy.java
That's a perfectly valid use case imho.
@laeubi if you need to interact with your specific event spy, you could
inject the implementation or another interface instead of the `EventSpy`
interface which is meant to be actually used by maven and does provide any
information.
> 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)
