Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Cannot Reproduce
-
Affects Version/s: 2.1-alpha-1
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:HideApache Maven 3.0.4 (r1232337; 2012-01-17 02:44:56-0600)
Maven home: /opt/maven
Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
Java home: /usr/java/jdk1.6.0_24/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "2.6.35.13-91.fc14.x86_64", arch: "amd64", family: "unix"
ShowApache Maven 3.0.4 (r1232337; 2012-01-17 02:44:56-0600) Maven home: /opt/maven Java version: 1.6.0_24, vendor: Sun Microsystems Inc. Java home: /usr/java/jdk1.6.0_24/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "2.6.35.13-91.fc14.x86_64", arch: "amd64", family: "unix"
Description
The FAQ suggests that using <classifier> tags with multiple executions of the attached-rpm goal allows multiple (different) rpms to be attached with classifiers.
However, this appears not to work intuitively. The first of these always seems to be copied/uploaded with a classifier of rpm (eg sla-rpms-1.2.20-SNAPSHOT-rpm.rpm) while subsequent rpms appear to have the proper classifier. (eg sla-rpms-1.2.20-SNAPSHOT-prod.rpm)
My expectation is that attaching a classifier to any given rpm would produce a file with that classifier in the repository. If not, then the -rpm classifier appended after the version number is superfluous since the .rpm extension already denotes an rpm.
Can you attach your pom?