[
https://issues.apache.org/jira/browse/MNG-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023408#comment-16023408
]
ASF GitHub Bot commented on MNG-6233:
-------------------------------------
Github user jdillon commented on the issue:
https://github.com/apache/maven/pull/116
Igor already created https://issues.apache.org/jira/browse/MNG-6233 but if
you really need another issue I can file one just to fix this specific problem.
Seems a bit odd though that you want an IT to apply a clear coding mistake
due to the ctor parameter being ignored and not setting the component causing
NPE when used. :-(
> 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
> Assignee: 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)
