[
https://issues.apache.org/jira/browse/PIVOT-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16574866#comment-16574866
]
Roger Whitcomb edited comment on PIVOT-1035 at 8/9/18 1:53 PM:
---------------------------------------------------------------
Committed this change:
Sending build.xml
Transmitting file data .done
Committing transaction...
Committed revision 1837729.
So that the latest manifest information is now:
{{Manifest-Version : 1.0}}
{{Ant-Version : Apache Ant 1.10.5}}
{{Created-By : 10.0.2+13 ("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_1837729}}
{{Permissions : all-permissions}}
{{Codebase : *}}
{{Caller-Allowable-Codebase : *}}
{{Application-Library-Allowable-Codebase : *}}
was (Author: rwhitcomb):
Committed this change:
Sending build.xml
Transmitting file data .done
Committing transaction...
Committed revision 1837729.
> 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)
