[
https://issues.apache.org/jira/browse/MNG-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16546883#comment-16546883
]
Guillermo Fernandes commented on MNG-6240:
------------------------------------------
I'm having this issue even using Maven 3.5.2 or 3.5.3 and maven-deploy-plugin
2.8.2. Could it be related to a particular plugin (besides maven-deploy-plugin)
or the project classpath? In particular this project has dependency to Aether
(it uses Aether to resolve dependencies programmatically).
> Duplicate components in plugin extension realm when plugin depends on
> maven-aether-resolver
> -------------------------------------------------------------------------------------------
>
> Key: MNG-6240
> URL: https://issues.apache.org/jira/browse/MNG-6240
> Project: Maven
> Issue Type: Bug
> Components: Class Loading
> Affects Versions: 3.5.0
> Reporter: Guillaume Boué
> Assignee: Guillaume Boué
> Priority: Major
> Fix For: 3.5.2
>
>
> When a plugin extension has a dependency on {{maven-aether-resolver}}, the
> components of this artifact are added into the plugin realm even though Maven
> Core already provides them. This is a regression introduced by the rename of
> this module to {{maven-resolver-provider}} in 3.5.0.
> This rename has kept all the classes of {{maven-aether-resolver}} for
> compatibility, therefore the old artifact name also needs to be exported by
> Maven Core in {{extension.xml}}.
> A visible side-effect of this is MDEPLOY-221, where the two
> {{MetadataGeneratorFactory}} components of {{maven-aether-provider}} (which
> are {{SnapshotMetadataGeneratorFactory}} and
> {{VersionsMetadataGeneratorFactory}}) are present twice as Guice bindings,
> and wrong metadata information is deployed as a consequence. This is due to
> the Flex Mojos plugin extension which depends on {{maven-aether-resolver}}
> used in the build.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
