[Commented] (MNG-6233) maven-resolver-provider mixes jsr330 and plexus annotations

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[Commented] (MNG-6233) maven-resolver-provider mixes jsr330 and plexus annotations

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/MNG-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015056#comment-16015056 ]

Igor Fedorenko commented on MNG-6233:
-------------------------------------

Pushed proposed change to https://git-wip-us.apache.org/repos/asf?p=maven.git;a=shortlog;h=refs/heads/MNG-6233_maven-resolver-provider-jsr330. Let me know if you agree/disagree to include this change in 3.5.1. Like I said, we've used this in our local version of maven for some time now without any problems. All ITs pass for me locally too.

> 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)