[ 
https://issues.apache.org/jira/browse/MSHARED-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14655246#comment-14655246
 ] 

Jörg Sesterhenn edited comment on MSHARED-432 at 8/5/15 12:19 PM:
------------------------------------------------------------------

The restriction of the Specification-Version format comes from here:
https://docs.oracle.com/javase/8/docs/api/java/lang/Package.html
and here:
https://docs.oracle.com/javase/8/docs/technotes/guides/versioning/spec/versioning2.html#wp90779

{quote}
Specification version numbers use a syntax that consists of positive decimal 
integers separated by periods ".", for example "2.0" or "1.2.3.4.5.6.7". ...
{quote}

There is also a statement, that the
{quote}
... implementation version strings have no specified syntax and should only be 
compared for equality with desired version identifiers. 
{quote}

So I guess changing only the former would fix this issue.


was (Author: joerg.sesterhenn):
The restriction of the Specification-Version format comes from here:
https://docs.oracle.com/javase/6/docs/api/java/lang/Package.html
{quote}
Specification version numbers use a syntax that consists of positive decimal 
integers separated by periods ".", for example "2.0" or "1.2.3.4.5.6.7". ...
{quote}

There is also a statement, that the
{quote}
... implementation version strings have no specified syntax and should only be 
compared for equality with desired version identifiers. 
{quote}

So I guess changing only the former would fix this issue.

> Maven Archiver creates invalid Implementation-/Specification-Version string 
> for SNAPSHOTs
> -----------------------------------------------------------------------------------------
>
>                 Key: MSHARED-432
>                 URL: https://issues.apache.org/jira/browse/MSHARED-432
>             Project: Maven Shared Components
>          Issue Type: Bug
>          Components: maven-archiver
>    Affects Versions: maven-archiver-2.6
>         Environment: Oracle Weblogic 12.x
>            Reporter: Jörg Sesterhenn
>
> Steps to reproduce:
> 1) Build any SNAPSHOT-version of a war or ear with the configuration shown 
> here to add implementation- and Specification-Version to the archives 
> metadata:
> http://maven.apache.org/shared/maven-archiver/examples/manifest.html
> The added Version-String looks like *1.0.0-SNAPSHOT* !
> 2) Deploy this archive in Weblogic 12.x
> This results in weblogic not deploying the archive and throwing the following 
> errors:
> {code}
> BEA-160142: The library at {0} has an illegal Specification-Version: {1}. The 
> Specification-Version must be a valid version string: int(.int)*, int >=0; 
> for example: 2.1.1
>     Cause: The Specification-Version for the library at {0} cannot be parsed.
>     Action: Fix the library Specification-Version to conform to the required 
> version string syntax.
>     Level: 1
>     Type: ERROR
>     Impact: J2EE
> BEA-160143: Library {0} has an illegal Specification-Version: {1}. The 
> Specification-Version must be a valid version string: int(.int)*, int >=0. 
> For example: 2.1.1.
>     Cause: The library cannot be statically deployed because its MBean has an 
> invalid Specification-Version.
>     Action: Undeploy the library and deploy it again with a correct 
> Specification-Version.
>     Level: 1
>     Type: ERROR
>     Impact: J2EE
> {code}
> see http://docs.oracle.com/middleware/1213/core/FMERR/chapter_bea_messages.htm
> _Proposed solution:_
> Omit the "-SNAPSHOT" String in the version metadata
> _Alternative  solution:_
> Replace "-SNAPSHOT" with ".TIMESTAMP", where TIMESTAMP consists only of 
> positive integers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to