[
https://issues.apache.org/jira/browse/MNG-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011158#comment-16011158
]
Robert Scholte commented on MNG-6233:
-------------------------------------
IIRC [~jvanzyl] prepared this on his system. However, JSR330 doesn't support
different configurations with the same implementation, like we do for
lifecycles. Not sure what happened to that part.
If Jason can apply it on the current sourcetree without issues, we could do
that. Otherwise let's go for a per-module upgrade, although I think it should
all fit within one release. That said, having 1 issue with a checklist for all
modules is good enough for me.
> maven-resolver-provider mixes jsr330 and plexus annotations
> -----------------------------------------------------------
>
> Key: MNG-6233
> URL: https://issues.apache.org/jira/browse/MNG-6233
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.3.9, 3.5.0
> Reporter: Igor Fedorenko
> Fix For: 3.5.1-candidate
>
>
> Mixed annotations confuse guice/sisu and result in hard to troubleshoot and
> impossible to workaround problems in applications that embed Maven core
> runtime, like m2e and gshell.
> I believe plugins annotations where left in the code by mistake so the plan
> is to update the code to use jsr330 exclusively and completely remove plexus
> annotations. This change is fully transparent to the users (and we've been
> using it internally for couple of months now).
> See also https://github.com/apache/maven/pull/116
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
