You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Benedict (JIRA)" <ji...@codehaus.org> on 2009/11/17 20:39:55 UTC
[jira] Created: (MNG-4452) Metadata for snapshots should include
classifier
Metadata for snapshots should include classifier
------------------------------------------------
Key: MNG-4452
URL: http://jira.codehaus.org/browse/MNG-4452
Project: Maven 2
Issue Type: Improvement
Components: Artifacts and Repositories
Affects Versions: 3.0-alpha-4, 2.2.1
Reporter: Paul Benedict
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-4452) Metadata for snapshots should include classifier
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy updated MNG-4452:
-------------------------------
Fix Version/s: 2.2.x (to be reviewed)
> Metadata for snapshots should include classifier
> ------------------------------------------------
>
> Key: MNG-4452
> URL: https://jira.codehaus.org/browse/MNG-4452
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-4
> Reporter: Paul Benedict
> Assignee: Benjamin Bentmann
> Fix For: 3.0, 2.2.x (to be reviewed)
>
> Attachments: nar-artifact-list.txt, nar-maven-metadata.xml, output
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4452) Metadata for snapshots should include
classifier
Posted by "Dan Tran (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198545#action_198545 ]
Dan Tran commented on MNG-4452:
-------------------------------
don't think 2.2.1 is affected. Just 3.0
> Metadata for snapshots should include classifier
> ------------------------------------------------
>
> Key: MNG-4452
> URL: http://jira.codehaus.org/browse/MNG-4452
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-4
> Reporter: Paul Benedict
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4452) Metadata for snapshots should include
classifier
Posted by "Andrei Pozolotin (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250857#action_250857 ]
Andrei Pozolotin commented on MNG-4452:
---------------------------------------
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>${barchart.version}</version>
<type>jar</type>
</dependency>
<dependency>
<groupId>com.barchart.udt</groupId>
<artifactId>barchart-udt4</artifactId>
<version>${barchart.version}</version>
<classifier>i386-Linux-g++-jni</classifier>
<type>nar</type>
</dependency>
<dependency>
<groupId>com.barchart.udt</groupId>
<artifactId>barchart-udt4</artifactId>
<version>${barchart.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
> Metadata for snapshots should include classifier
> ------------------------------------------------
>
> Key: MNG-4452
> URL: http://jira.codehaus.org/browse/MNG-4452
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-4
> Reporter: Paul Benedict
> Assignee: Benjamin Bentmann
> Fix For: 3.0
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4452) Metadata for snapshots should include
classifier
Posted by "Leon Franzen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252396#action_252396 ]
Leon Franzen commented on MNG-4452:
-----------------------------------
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.ula.comcast.net: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.cvs.ula.comcast.net: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?
> Metadata for snapshots should include classifier
> ------------------------------------------------
>
> Key: MNG-4452
> URL: http://jira.codehaus.org/browse/MNG-4452
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-4
> Reporter: Paul Benedict
> Assignee: Benjamin Bentmann
> Fix For: 3.0
>
> Attachments: nar-artifact-list.txt, nar-maven-metadata.xml, output
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MNG-4452) Metadata for snapshots
should include classifier
Posted by "Leon Franzen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252396#action_252396 ]
Leon Franzen edited comment on MNG-4452 at 1/21/11 4:59 PM:
------------------------------------------------------------
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?
was (Author: leon_franzen):
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.ula.comcast.net: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.cvs.ula.comcast.net: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?
> Metadata for snapshots should include classifier
> ------------------------------------------------
>
> Key: MNG-4452
> URL: http://jira.codehaus.org/browse/MNG-4452
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-4
> Reporter: Paul Benedict
> Assignee: Benjamin Bentmann
> Fix For: 3.0
>
> Attachments: nar-artifact-list.txt, nar-maven-metadata.xml, output
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-4452) Metadata for snapshots should include
classifier
Posted by "Leon Franzen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leon Franzen updated MNG-4452:
------------------------------
Attachment: nar-maven-metadata.xml
nar-artifact-list.txt
output
The state of the snapshot repository during the Maven build shown in the file "output" (attached)
> Metadata for snapshots should include classifier
> ------------------------------------------------
>
> Key: MNG-4452
> URL: http://jira.codehaus.org/browse/MNG-4452
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-4
> Reporter: Paul Benedict
> Assignee: Benjamin Bentmann
> Fix For: 3.0
>
> Attachments: nar-artifact-list.txt, nar-maven-metadata.xml, output
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4452) Metadata for snapshots should include
classifier
Posted by "Andrei Pozolotin (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252332#action_252332 ]
Andrei Pozolotin commented on MNG-4452:
---------------------------------------
Leon:
my woraround is use direct repo access and NOT to use repo-to-repo proxy:
https://issues.sonatype.org/browse/NEXUS-4055
Andrei
> Metadata for snapshots should include classifier
> ------------------------------------------------
>
> Key: MNG-4452
> URL: http://jira.codehaus.org/browse/MNG-4452
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-4
> Reporter: Paul Benedict
> Assignee: Benjamin Bentmann
> Fix For: 3.0
>
> Attachments: nar-artifact-list.txt, nar-maven-metadata.xml, output
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-4452) Metadata for snapshots should include
classifier
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4452.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0-beta-4
Assignee: Benjamin Bentmann
Fixed in [r995057|http://svn.apache.org/viewvc?view=revision&revision=995057].
> Metadata for snapshots should include classifier
> ------------------------------------------------
>
> Key: MNG-4452
> URL: http://jira.codehaus.org/browse/MNG-4452
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-4
> Reporter: Paul Benedict
> Assignee: Benjamin Bentmann
> Fix For: 3.0-beta-4
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4452) Metadata for snapshots should include
classifier
Posted by "Andrei Pozolotin (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250858#action_250858 ]
Andrei Pozolotin commented on MNG-4452:
---------------------------------------
forgot to mention: of course, this relates to SNAPSHOT artifacts only
> Metadata for snapshots should include classifier
> ------------------------------------------------
>
> Key: MNG-4452
> URL: http://jira.codehaus.org/browse/MNG-4452
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-4
> Reporter: Paul Benedict
> Assignee: Benjamin Bentmann
> Fix For: 3.0
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-4452) Metadata for snapshots should include classifier
Posted by "Lukasz Szelag (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285802#comment-285802 ]
Lukasz Szelag commented on MNG-4452:
------------------------------------
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
> Metadata for snapshots should include classifier
> ------------------------------------------------
>
> Key: MNG-4452
> URL: https://jira.codehaus.org/browse/MNG-4452
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-4
> Reporter: Paul Benedict
> Assignee: Benjamin Bentmann
> Fix For: 3.0
>
> Attachments: nar-artifact-list.txt, nar-maven-metadata.xml, output
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4452) Metadata for snapshots should include
classifier
Posted by "Dan Tran (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198555#action_198555 ]
Dan Tran commented on MNG-4452:
-------------------------------
confirm, it only affects maven 3
> Metadata for snapshots should include classifier
> ------------------------------------------------
>
> Key: MNG-4452
> URL: http://jira.codehaus.org/browse/MNG-4452
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-4
> Reporter: Paul Benedict
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4452) Metadata for snapshots should include
classifier
Posted by "Leon Franzen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251547#action_251547 ]
Leon Franzen commented on MNG-4452:
-----------------------------------
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?
> Metadata for snapshots should include classifier
> ------------------------------------------------
>
> Key: MNG-4452
> URL: http://jira.codehaus.org/browse/MNG-4452
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-4
> Reporter: Paul Benedict
> Assignee: Benjamin Bentmann
> Fix For: 3.0
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4452) Metadata for snapshots should include
classifier
Posted by "Dan Tran (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198562#action_198562 ]
Dan Tran commented on MNG-4452:
-------------------------------
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
> Metadata for snapshots should include classifier
> ------------------------------------------------
>
> Key: MNG-4452
> URL: http://jira.codehaus.org/browse/MNG-4452
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-4
> Reporter: Paul Benedict
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4452) Metadata for snapshots should include
classifier
Posted by "Andrei Pozolotin (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250856#action_250856 ]
Andrei Pozolotin commented on MNG-4452:
---------------------------------------
Benjamin:
just to confirm, is it fixed in 3.0.1? the issue still affecting me
thanks;
Andrei
> Metadata for snapshots should include classifier
> ------------------------------------------------
>
> Key: MNG-4452
> URL: http://jira.codehaus.org/browse/MNG-4452
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-4
> Reporter: Paul Benedict
> Assignee: Benjamin Bentmann
> Fix For: 3.0
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4452) Metadata for snapshots should include
classifier
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234627#action_234627 ]
Benjamin Bentmann commented on MNG-4452:
----------------------------------------
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|http://svn.apache.org/viewvc?view=revision&revision=995081] to revert to the 1.0.0 format during deployment if needed.
> Metadata for snapshots should include classifier
> ------------------------------------------------
>
> Key: MNG-4452
> URL: http://jira.codehaus.org/browse/MNG-4452
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-4
> Reporter: Paul Benedict
> Assignee: Benjamin Bentmann
> Fix For: 3.0-beta-4
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4452) Metadata for snapshots should include
classifier
Posted by "Paul Benedict (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198548#action_198548 ]
Paul Benedict commented on MNG-4452:
------------------------------------
Dan, check you check to verify?
> Metadata for snapshots should include classifier
> ------------------------------------------------
>
> Key: MNG-4452
> URL: http://jira.codehaus.org/browse/MNG-4452
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-4
> Reporter: Paul Benedict
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4452) Metadata for snapshots should include
classifier
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198556#action_198556 ]
Benjamin Bentmann commented on MNG-4452:
----------------------------------------
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.
> Metadata for snapshots should include classifier
> ------------------------------------------------
>
> Key: MNG-4452
> URL: http://jira.codehaus.org/browse/MNG-4452
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-4
> Reporter: Paul Benedict
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MNG-4452) Metadata for snapshots
should include classifier
Posted by "Paul Benedict (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198548#action_198548 ]
Paul Benedict edited comment on MNG-4452 at 11/17/09 2:53 PM:
--------------------------------------------------------------
Dan, can you please check to verify?
was (Author: paul4christ79):
Dan, check you check to verify?
> Metadata for snapshots should include classifier
> ------------------------------------------------
>
> Key: MNG-4452
> URL: http://jira.codehaus.org/browse/MNG-4452
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-4
> Reporter: Paul Benedict
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4452) Metadata for snapshots should include
classifier
Posted by "Andrei Pozolotin (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253016#action_253016 ]
Andrei Pozolotin commented on MNG-4452:
---------------------------------------
Leon:
according to this:
https://issues.sonatype.org/browse/NEXUS-4055
sonatype folks fixed this in trunk; you may want to build nexus;
Andrei
> Metadata for snapshots should include classifier
> ------------------------------------------------
>
> Key: MNG-4452
> URL: http://jira.codehaus.org/browse/MNG-4452
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-4
> Reporter: Paul Benedict
> Assignee: Benjamin Bentmann
> Fix For: 3.0
>
> Attachments: nar-artifact-list.txt, nar-maven-metadata.xml, output
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4452) Metadata for snapshots should include
classifier
Posted by "Andrei Pozolotin (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253017#action_253017 ]
Andrei Pozolotin commented on MNG-4452:
---------------------------------------
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
> Metadata for snapshots should include classifier
> ------------------------------------------------
>
> Key: MNG-4452
> URL: http://jira.codehaus.org/browse/MNG-4452
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-4
> Reporter: Paul Benedict
> Assignee: Benjamin Bentmann
> Fix For: 3.0
>
> Attachments: nar-artifact-list.txt, nar-maven-metadata.xml, output
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4452) Metadata for snapshots should include
classifier
Posted by "Andrei Pozolotin (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253015#action_253015 ]
Andrei Pozolotin commented on MNG-4452:
---------------------------------------
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
> Metadata for snapshots should include classifier
> ------------------------------------------------
>
> Key: MNG-4452
> URL: http://jira.codehaus.org/browse/MNG-4452
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-4
> Reporter: Paul Benedict
> Assignee: Benjamin Bentmann
> Fix For: 3.0
>
> Attachments: nar-artifact-list.txt, nar-maven-metadata.xml, output
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira