maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joerg Schaible (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MSHARED-191) Specification-Version must not contain "-SNAPSHOT"
Date Tue, 29 Mar 2011 06:30:22 GMT

    [ http://jira.codehaus.org/browse/MSHARED-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261787#action_261787
] 

Joerg Schaible commented on MSHARED-191:
----------------------------------------

At least there is a workaround: http://article.gmane.org/gmane.comp.jakarta.commons.devel/113911

> Specification-Version must not contain "-SNAPSHOT"
> --------------------------------------------------
>
>                 Key: MSHARED-191
>                 URL: http://jira.codehaus.org/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)
>            Reporter: Romain Buquet
>         Attachments: patch maven-archiver
>
>
> 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 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

       

Mime
View raw message