goutamadwant opened a new pull request, #13011: URL: https://github.com/apache/maven/pull/13011
Fixes #10677 ## Description Add Maven-owned repository event and listener APIs without exposing Maven Resolver types through the public API. The implementation bridges all 19 Resolver repository event types and maps artifacts, metadata, repositories, paths, exceptions, and request traces to Maven API types. Listener registration is thread-safe and scoped to the underlying Resolver session, so derived Maven sessions share the same registration lifecycle. A failure in one listener does not prevent other listeners from receiving an event. ## Tests - Added coverage for every repository event type and field mapping. - Added coverage for listener registration, removal, derived-session scope, exception isolation, and bootstrap behavior. - Focused tests: 18 passed. - `mvn --batch-mode verify`: passed. - Core IT: 1,059 tests passed under JDK 26. The two JDK-sensitive failures were rerun under JDK 21 and all 4 test methods passed. Following this checklist to help us incorporate your contribution quickly and easily: - [x] This pull request addresses one issue without unrelated changes. - [x] The description explains what the pull request does, how, and why. - [x] The commit has a meaningful subject and body. - [x] Unit tests cover the behavioral changes. - [x] `mvn verify` passes. - [ ] The complete Core IT command passed in one environment. See the JDK-specific results above. - [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). [core-its]: https://maven.apache.org/core-its/core-it-suite/ -- 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]
