gnodet commented on issue #13646: URL: https://github.com/apache/maven/issues/13646#issuecomment-6763843118
Thanks for the interest @codewithsinchana. Before this can be implemented, we need to resolve a prerequisite: not all services that use `Request`/`Result` should fire `RequestEvent`. The factory services (`ArtifactFactory`, `ArtifactCoordinatesFactory`, `DependencyCoordinatesFactory`) use `Request` objects but are really just typed constructors — firing events for every coordinate creation would add overhead and noise. I've filed #13943 to introduce an `OperationService` marker interface that distinguishes observable services (resolvers, builders, deployers — significant I/O, side effects, measurable duration) from utility/factory services (pure transformations, high frequency). Once that's in place, `RequestEvent` gets a clean rule: fire for every `OperationService` call, skip everything else. No per-service opt-in/opt-out ambiguity. So #13943 should land first, then this issue can be implemented on top of it. _Fully automatic review from Claude Code_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
