maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Edwards (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-6240) Duplicate components in plugin extension realm when plugin depends on maven-aether-resolver
Date Tue, 26 Sep 2017 15:32:00 GMT

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

David Edwards commented on MNG-6240:
------------------------------------

I am having deployment issues (see [Maven 3.5.0 causes major deployment issues|https://github.com/travis-ci/travis-ci/issues/8499]
for build logs, etc) using 3.5.0 on Travis CI, which has lead me to this bug report. The symptoms
are that when maven-deploy-plugin runs, the downloads and uploads of metadata get repeated
many times (upwards of 10 times per module), which eventually results in our repository (Bintray)
rejecting requests with a 405. Rolling back to 3.3.9 resolves the problem. I also found a
mailing list thread ([Excessive download/upload of maven-metadata.xml during maven deploy|http://mail-archives.apache.org/mod_mbox/maven-users/201705.mbox/%3CCAPCjjnFwyKPdfkr9ke6GORfXw2r_26z8pO5X%2BHFtHbSOGyRssA%40mail.gmail.com%3E])
with no conclusion that sounds similar, from after the release of 3.5.0.

Does this sound like it will be resolved by the fix for this issue in 3.5.1, or should I create
a new issue?

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

Mime
View raw message