Metadata for snapshots should include classifier

don't think 2.2.1 is affected. Just 3.0

Dan, can you please check to verify?

Not sure what exactly you consider as being affected, the metadata used by Maven 2 and 3 is the same. Maven 3.0 does not support non-unique snapshots but the general problem with the metadata exists in all existing Maven versions.

sorry about the confusion. This issue should mainly raise concern where maven 3 removes non-unique snapshot feature, and does not provide an alternative.

deploy non-unique snapshot still works with 2.2.1

Fixed in r995057.

To support interop with existing repository managers that don't know about the new format but try to process it on the server side, the system property maven.metadata.legacy=true|false has been added in r995081 to revert to the 1.0.0 format during deployment if needed.

Benjamin:
just to confirm, is it fixed in 3.0.1? the issue still affecting me
thanks;
Andrei

I guess, I must clarify:

1) yes I see in 3.0.1 that shapshots metadata does includes classifier;

2) the problem is that resolver still does not find attached artifacts form previous deployments;

for example, this is repo metadata after 2 deployments:

note, that artifacts of interest are (build 83 and 84):

com.barchart.udt:barchart-udt4:1.0.2-20110108.023638-83:i386-Linux-g++-jni:nar
com.barchart.udt:barchart-udt4:1.0.2-20110108.023723-84:amd64-Linux-g++-jni:nar

##############################################################

<metadata modelVersion="1.1.0">
<groupId>com.barchart.udt</groupId>
<artifactId>barchart-udt4</artifactId>
<version>1.0.2-SNAPSHOT</version>
−
<versioning>
−
<snapshot>
<timestamp>20110108.023723</timestamp>
<buildNumber>84</buildNumber>
</snapshot>
<lastUpdated>20110108023723</lastUpdated>
−
<snapshotVersions>
−
<snapshotVersion>
<extension>jar</extension>
<value>1.0.2-20110108.023723-84</value>
<updated>20110108023723</updated>
</snapshotVersion>
−
<snapshotVersion>
<extension>pom</extension>
<value>1.0.2-20110108.023723-84</value>
<updated>20110108023723</updated>
</snapshotVersion>
−
<snapshotVersion>
<classifier>noarch</classifier>
<extension>nar</extension>
<value>1.0.2-20110108.023723-84</value>
<updated>20110108023723</updated>
</snapshotVersion>
−
<snapshotVersion>
<classifier>i386-Linux-g++-jni</classifier>
<extension>nar</extension>
<value>1.0.2-20110108.023638-83</value>
<updated>20110108023638</updated>
</snapshotVersion>
−
<snapshotVersion>
<classifier>amd64-Linux-g++-jni</classifier>
<extension>nar</extension>
<value>1.0.2-20110108.023723-84</value>
<updated>20110108023723</updated>
</snapshotVersion>
</snapshotVersions>
</versioning>
</metadata>

##############################################################

and this is dependency declaration, I want 1 jar and 2 nar, platform dependent:

##############################################################

<dependency>
<groupId>com.barchart.udt</groupId>
<artifactId>barchart-udt4</artifactId>
<version>$

</version>
<classifier>i386-Linux-g++-jni</classifier>
<type>nar</type>
</dependency>

<dependency>
<groupId>com.barchart.udt</groupId>
<artifactId>barchart-udt4</artifactId>
<version>$

</version>
<classifier>amd64-Linux-g++-jni</classifier>
<type>nar</type>
</dependency>

##############################################################

and this is the error:

##############################################################

[INFO] Scanning for projects...
[INFO] snapshot com.barchart.udt:barchart-udt4-parent:1.0.0-SNAPSHOT: checking for updates from sonatype-nexus-snapshots
[INFO] ------------------------------------------------------------------------
[INFO] Building Unnamed - com.barchart.udt:barchart-udt4-bundle:jar:1.0.0-SNAPSHOT
[INFO] task-segment: [validate]
[INFO] ------------------------------------------------------------------------
[INFO] snapshot com.barchart.udt:barchart-udt4:1.0.2-SNAPSHOT: checking for updates from sonatype-nexus-snapshots
Downloading: https://oss.sonatype.org/content/repositories/snapshots/com/barchart/udt/barchart-udt4/1.0.2-SNAPSHOT/barchart-udt4-1.0.2-20110108.023723-84.pom

Downloading: https://oss.sonatype.org/content/repositories/snapshots/com/barchart/udt/barchart-udt4/1.0.2-SNAPSHOT/barchart-udt4-1.0.2-20110108.023723-84.jar
78K downloaded (barchart-udt4-1.0.2-20110108.023723-84.jar)
Downloading: https://oss.sonatype.org/content/repositories/snapshots/com/barchart/udt/barchart-udt4/1.0.2-SNAPSHOT/barchart-udt4-1.0.2-20110108.023723-84-i386-Linux-g++-jni.nar
Downloading: https://oss.sonatype.org/content/repositories/snapshots/com/barchart/udt/barchart-udt4/1.0.2-SNAPSHOT/barchart-udt4-1.0.2-20110108.023723-84-amd64-Linux-g++-jni.nar

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

##############################################################

in other words, the resolver tries to find

barchart-udt4-1.0.2-20110108.023723-84-i386-Linux-g++-jni.nar
and
barchart-udt4-1.0.2-20110108.023723-84-amd64-Linux-g++-jni.nar

both from latest build #84, instead of looking through the versioning
in order to find the file that actually exists in build #83:

barchart-udt4-1.0.2-20110108.023638-83:i386-Linux-g++-jni.nar

forgot to mention: of course, this relates to SNAPSHOT artifacts only

We are seeing exactly the same problem as Andrei in Maven 3.0.1 with platform dependent nar builds. This is a critical blocker for us.

By reconfiguring our settings.xml to work around the inability of Nexus to provide the new classifier/type specific metadata information through a repository-group, we are now stuck on this issue. Is there a way to set the build number at deploy time to work around this issue?

The state of the snapshot repository during the Maven build shown in the file "output" (attached)

Leon:
my woraround is use direct repo access and NOT to use repo-to-repo proxy:
https://issues.sonatype.org/browse/NEXUS-4055
Andrei

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?

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

Leon:

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

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

Andrei

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

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