Uploaded image for project: 'Maven'
  1. Maven
  2. MNG-6240

Duplicate components in plugin extension realm when plugin depends on maven-aether-resolver

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.5.0
    • 3.5.2
    • Class Loading
    • None

    Description

      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.

      Attachments

        1. maven-metadata.png
          50 kB
          Stefan Cordes
        2. jenkins-log.png
          343 kB
          Stefan Cordes
        3. Nexus-Storage.png
          83 kB
          Stefan Cordes
        4. partly-jenkins-log.txt
          2 kB
          Stefan Cordes

        Issue Links

          Activity

            People

              gboue Guillaume Boué
              gboue Guillaume Boué
              Votes:
              4 Vote for this issue
              Watchers:
              29 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: