[
https://issues.apache.org/jira/browse/MNG-7479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536985#comment-17536985
]
ASF GitHub Bot commented on MNG-7479:
-------------------------------------
hboutemy commented on PR #740:
URL: https://github.com/apache/maven/pull/740#issuecomment-1126664314
how do you expect filtering to happen to know which instance of EventSpy is
expected in your Mojo instance? There are thousands of EvenSpy instances, even
when you filter only a certain type
definitely, the lifecycle of EventSpy objects seems completely not adapted
to using IoC injection to me
Perhaps this study about LifecycleParticipant could help you
https://maven.apache.org/studies/extension-demo/
> 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)
