[jira] [Updated] (MNG-6898) Convert DefaultLifecyclePluginAnalyzer to JSR 330

["Michael Osipov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MNG-6898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov updated MNG-6898:
--------------------------------
        Parent: MNG-5577
    Issue Type: Sub-task  (was: Improvement)

> Convert DefaultLifecyclePluginAnalyzer to JSR 330
> -------------------------------------------------
>
>                 Key: MNG-6898
>                 URL: https://issues.apache.org/jira/browse/MNG-6898
>             Project: Maven
>          Issue Type: Sub-task
>          Components: core
>    Affects Versions: 3.6.3
>            Reporter: Joseph Walton
>            Priority: Major
>
> Convert {{DefaultLifecyclePluginAnalyzer}} in {{maven-core}} to JSR 330 annotations. This follows on from MNG-5577, which converted the other classes.
> The complication here is that, with the annotations changed, the {{lifecycleMappings}} {{Map}} is no longer getting filtered by sisu.plexus's {{RealmFilteredBeans}}. That means extensions added in one module will appear in all of them, which makes [{{MavenITmng4385LifecycleMappingFromExtensionInReactorTest}}|https://github.com/apache/maven-integration-testing/blob/6e480ac3a436bf4f3624f36935578966430c654c/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng4385LifecycleMappingFromExtensionInReactorTest.java] fail.
> From what I can see, the only place a {{RealmFilteredBeans}} is used during injection is when the resource is located through {{DefaultPlexusBeanLocator}}. However, that's not the case after that field switches from {{@Requirement}} to {{@Inject}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)