[
https://issues.apache.org/jira/browse/MNG-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158685#comment-16158685
]
Christoph Amshoff commented on MNG-6240:
----------------------------------------
I'm sorry if this is annoying, but this issue is clearly a blocker since it
randomly breaks builds, and going back to Maven 3.3.9 is not always an option.
So what exactly is the reason we can't get some kind of release where this is
fixed, nearly 3 months after the issue has been marked as closed? 3.5.1-alpha
or such would be fine in case some other planned issues still need a review.
Moreover, I agree with Jay mann's comment on MDEPLOY-221 that the version 3.5.0
should be marked as buggy on the Maven homepage, or perhaps even revoked.
Please, don't let Maven users run into this without giving a heads-up, and
without a chance to get around it!
> 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é
> Fix For: 3.5.1
>
>
> 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
(v6.4.14#64029)
