Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-12238

Partial coordinates for maven metadata

    XMLWordPrintable

    Details

      Description

      Background
      1. A user creates a hosted repository, and a content selector permission based on a groupId, e.g. format == "maven2" and coordinate.groupId =^ "my.test"
      2. The user attempt to upload a .jar, via

      mvn org.apache.maven.plugins:maven-deploy-plugin:deploy-file \
        -Dfile=testing.jar -DrepositoryId=testing -Durl=$TESTURL \
        -DgroupId=my.test -Dversion=1.0 -Dartifact=testing -Dtype=jar
      

      3. Deployment fails:

      Access denied to:
      http://nexus-lab.home.bardicgrove.org/repository/maven-releases/my/test/testing/maven-metadata.xml,
      

      The reason for this is that maven-metadata.xml files don't have any coordinates associated with them for the purposes of content selector evaluation. The workaround is that users can create a more complicated content selector that ORs the groupId with a path, but that's unnecessarily fiddly.

      Acceptance

      • maven-metadata.xml files have partial component coordinates assigned to them (just groupId and artifactId, I guess?) so that the scenario, above, works correctly and the client can update metadata.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mdodgson Mark Dodgson
              Reporter:
              mprescott Michael Prescott
              Last Updated By:
              Rich Seddon
              Team:
              NXRM - Cypher
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response:

                  tigCommentSecurity.panel-title