cstamas commented on pull request #548: URL: https://github.com/apache/maven/pull/548#issuecomment-925139255
> I'm not sure if there's much difference between using the PlexusContainer api or the Sisu one. Is the goal to completely get rid of the `org.codehaus.plexus` package ? I thought (but I may be wrong) that the idea was more to get rid of the `@Component` and `@Requirement` annotations. We will probably never be able to get rid of `org.codehaus.plexus` package (utils, Xpp3Dom, etc) -- at least not on short run. Plexus Container on the other hand, is also very proliferated in Maven codebase, so again, hard nut. So IMO this is not our goal on short or mid term. Yes, the idea was to change Plexus component to JSR330 annotated one, but I did it while thinking about Plexus Container itself as a bit of "deprecated" (not yet, but kinda): so better to lower exposure -- or rather, not introduce NEW exposure/code using it -- but it circumvent it. Sill, we should try to get rid of as much deprecated stuff as we can (we still have code using org.sonatype.aether, using javadoc tags for plexus components, and so on). And I tend to classify PlexusContainer as deprecated as well, in a way: if possible, do not touch it, ONLY when other solution is not 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]
