Maven 2 & 3
  1. Maven 2 & 3
  2. MNG-4452

Metadata for snapshots should include classifier

    Details

    • Complexity:
      Intermediate
    • Number of attachments :
      3

      Description

      Please see the whole conversation here:
      http://old.nabble.com/Multi-Platform-snapshots-td25295999.html

      Essentially, an artifact's classifier isn't included in the repository's metadata of a snapshot. This makes it difficult (impossible?) to deploy multiply snapshots with different classifiers. The primary use case is to continuously build an artifact for different environments.

      1. nar-artifact-list.txt
        103 kB
        Leon Franzen
      2. nar-maven-metadata.xml
        2 kB
        Leon Franzen
      3. output
        232 kB
        Leon Franzen

        Issue Links

          Activity

          Hide
          Leon Franzen added a comment - - edited

          Then I think perhaps I am not configuring my settings.xml properly to work around the problem. I am still referencing a repository group but have tried to include a direct repo reference to my snapshot repository.

          <settings>
          <mirrors>
          <mirror>
          <id>nexus</id>
          <mirrorOf>*,!snapshots</mirrorOf>
          <url>http://nexus:8081/nexus/content/groups/public</url> <!-- My problematic repo-group -->
          </mirror>
          </mirrors>
          <profiles>
          <profile>
          <id>nexus</id>
          <repositories>
          <repository>
          <id>snapshots</id>
          <url>http://nexus:8081/nexus/content/repositories/snapshots</url> <!-- My snapshot repo -->
          <releases>
          <enabled>false</enabled>
          </releases>
          <snapshots>
          <enabled>true</enabled>
          </snapshots>
          </repository>
          ...

          Andrei, how were you specifically able to work around the issue? Are you not using a group?

          Show
          Leon Franzen added a comment - - edited Then I think perhaps I am not configuring my settings.xml properly to work around the problem. I am still referencing a repository group but have tried to include a direct repo reference to my snapshot repository. <settings> <mirrors> <mirror> <id>nexus</id> <mirrorOf>*,!snapshots</mirrorOf> <url> http://nexus:8081/nexus/content/groups/public </url> <!-- My problematic repo-group --> </mirror> </mirrors> <profiles> <profile> <id>nexus</id> <repositories> <repository> <id>snapshots</id> <url> http://nexus:8081/nexus/content/repositories/snapshots </url> <!-- My snapshot repo --> <releases> <enabled>false</enabled> </releases> <snapshots> <enabled>true</enabled> </snapshots> </repository> ... Andrei, how were you specifically able to work around the issue? Are you not using a group?
          Hide
          Andrei Pozolotin added a comment -

          Leon:

          in my case:

          1) my "real repo" is sonaytpe oss;

          2) my "proxy repo" is internal corporate repo which was going after sonatype oss;

          Andrei

          Show
          Andrei Pozolotin added a comment - Leon: in my case: 1) my "real repo" is sonaytpe oss; 2) my "proxy repo" is internal corporate repo which was going after sonatype oss; Andrei
          Hide
          Andrei Pozolotin added a comment -

          Leon:

          according to this:
          https://issues.sonatype.org/browse/NEXUS-4055

          sonatype folks fixed this in trunk; you may want to build nexus;

          Andrei

          Show
          Andrei Pozolotin added a comment - Leon: according to this: https://issues.sonatype.org/browse/NEXUS-4055 sonatype folks fixed this in trunk; you may want to build nexus; Andrei
          Hide
          Andrei Pozolotin added a comment -

          Leon:

          I tried to send you email (listed on this site); but it got bounced;

          I wanted to ask you if you were able to solve the following nar issue:
          https://issues.sonatype.org/browse/NAR-181

          thank you;

          Andrei

          Show
          Andrei Pozolotin added a comment - Leon: I tried to send you email (listed on this site); but it got bounced; I wanted to ask you if you were able to solve the following nar issue: https://issues.sonatype.org/browse/NAR-181 thank you; Andrei
          Hide
          Lukasz Szelag added a comment -

          I'm also experiencing the same issue (Maven 2.2.1 and Archiva 1.3.5). As I'm not ready to switch to Maven 3.x yet - is there a patch for 2.2.1 that provides a fix? I'm using this functionality (classifier) to name artifacts for different environments.

          Thanks,
          Lukasz

          Show
          Lukasz Szelag added a comment - I'm also experiencing the same issue (Maven 2.2.1 and Archiva 1.3.5). As I'm not ready to switch to Maven 3.x yet - is there a patch for 2.2.1 that provides a fix? I'm using this functionality (classifier) to name artifacts for different environments. Thanks, Lukasz

            People

            • Assignee:
              Benjamin Bentmann
              Reporter:
              Paul Benedict
            • Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: