[
https://issues.apache.org/jira/browse/MSHARED-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15076173#comment-15076173
]
Hudson commented on MSHARED-191:
--------------------------------
SUCCESS: Integrated in maven-shared #845 (See
[https://builds.apache.org/job/maven-shared/845/])
[MSHARED-191] Specification-Version must not contain "-SNAPSHOT" (michaelo:
[http://svn.apache.org/viewvc/?view=rev&rev=1722470])
* maven-archiver/src/main/java/org/apache/maven/archiver/MavenArchiver.java
* maven-archiver/src/site/apt/examples/manifest.apt
* maven-archiver/src/site/xdoc/index.xml.vm
* maven-archiver/src/test/java/org/apache/maven/archiver/MavenArchiverTest.java
* maven-archiver/src/test/java/org/apache/maven/archiver/MockArtifact.java
> Specification-Version must not contain "-SNAPSHOT"
> --------------------------------------------------
>
> Key: MSHARED-191
> URL: https://issues.apache.org/jira/browse/MSHARED-191
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
> Affects Versions: maven-archiver-2.4.1
> Environment: Ubuntu 10.10, Maven 2.2.1 and Maven 3.0.3, OpenJDK
> Runtime Environment (IcedTea6 1.9.7) (6b20-1.9.7-0ubuntu1) (64 bits)
> Mint 17.1, Java HotSpot(TM) 64-Bit Server VM (build 20.0-b11, mixed mode),
> Maven 3.2.5
> Reporter: Romain Buquet
> Assignee: Michael Osipov
> Priority: Critical
> Fix For: maven-archiver-3.0.1
>
> Attachments: MSHARED-191.patch
>
>
> When building an artifact with a SNAPSHOT version,
> Specification-Version and Implementation-Version are both set to
> $\{pom.version\} (as described in the documentation).
> But this will break the deployment in a container like WebLogic Server 10.3.4.
> This behavior is compliant with specification
> http://download.oracle.com/javase/6/docs/technotes/guides/versioning/spec/versioning2.html#wp89939
> where it is said that "Specification version numbers use a Dewey decimal
> notation consisting of numbers seperated by periods"
> Further in this spec, in ยง "1.5.10 Rationale for limiting Implementation
> version numbers to identity", it is explained why Implementation-Version need
> to be compared strictly for equality.
> So we can understand that:
> * Specification-Version must NOT have "-SNAPSHOT" suffix. This is legal to
> keep only the beginning of $\{pom.version\}, because it represents the spec
> version, not the build ;
> * Implementation-Version has to be set to $\{pom.version\} to represent the
> exact version of the build.
> This used to be the behavior in Maven 1:
> http://maven.apache.org/maven-1.x/plugins/jar/manifest.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
