gnodet commented on pull request #616: URL: https://github.com/apache/maven/pull/616#issuecomment-976683464
> I know you've gone through the effort here to get the caching extension to work from `lib/ext` but is that how you envision it working? If you have a large organization with many developers I think it would be preferable to configure it from the POM no? Or does this extension do some capabilities earlier than an extension in the form of a plugin? > > I realize the way extensions in `lib/ext` versus being defined in a plugin have always worked differently, and I can't off the the top of my head remember why we did that, but maybe they should be aligned so that artifacts are resolved in the same way. Currently, they do not work exactly the same. Some beans are discovered a bit too early in the process. For example `EventSpy` implementations can't be registered inside an extension discovered from the POM afaik. This is also true for a few other beans. The new `plugin` class loading strategy that I propose aims at reconciling the class loaders difference. I also plan to raise a PR so that some beans are discovered later in the process inside the `@SessionScoped`, such as `MojoExecutor` and related beans. This would allow the caching extension from #607 to be registered in the POM, which is not currently possible. -- 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]
