[
https://issues.apache.org/jira/browse/PIVOT-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518528#comment-16518528
]
Roger Whitcomb commented on PIVOT-1035:
---------------------------------------
We could set the "Specification-Version" to just be the "2.1.0" value (without
the build number), but I think we have to keep the "Implementation-Version"
as-is because ApplicationContext expects it to be a "Version" value....
Add three of the "Specification" fields in the .jar file manifests:
* Specification-Title
* Specification-Version
* Specification-Vendor
to make the manifest as complete as possible.
Sending build.xml
Transmitting file data .done
Committing transaction...
Committed revision 1833942.
Now the manifest looks like:
Manifest-Version : 1.0
Ant-Version : Apache Ant 1.9.7
Created-By : 1.8.0_131-b11 (Oracle Corporation)
Sealed : true
Specification-Title : Apache Pivot Core
Specification-Version : 2.1.0
Specification-Vendor : The Apache Software Foundation
Implementation-Vendor-Id : org.apache
Implementation-Vendor : The Apache Software Foundation
Implementation-Title : Apache Pivot Core
Implementation-Version : 2.1.0_20181711230
Permissions : all-permissions
Codebase : *
Caller-Allowable-Codebase : *
Application-Library-Allowable-Codebase : *
> Add a real build number to the Pivot (internal) version
> -------------------------------------------------------
>
> Key: PIVOT-1035
> URL: https://issues.apache.org/jira/browse/PIVOT-1035
> Project: Pivot
> Issue Type: Improvement
> Components: wtk
> Reporter: Roger Whitcomb
> Assignee: Roger Whitcomb
> Priority: Minor
>
> Right now the internal Pivot version number looks like this: 2.1.0_00, where
> the final "00" is always 00. It would be helpful if we could implement a
> "real" build number to track changes during development (for instance). I'm
> not sure how this should work, but beginning with the Ant "<buildnumber/>"
> task might be a start.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
