[
https://issues.apache.org/jira/browse/PIVOT-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518500#comment-16518500
]
Roger Whitcomb commented on PIVOT-1035:
---------------------------------------
The "Implementation-Version" field looks like it can be any arbitrary text.
But in ApplicationContext it is getting this value and parsing it as a
"Version"... (line 1867 in the static initialization of the class), so it
pretty much has to correspond to our understanding of a "Version" string
(org.apache.pivot.util.Version).
So, I have just updated our own "Version" class to deal with the build number
in the format I just implemented (change from "short" to "long"):
Sending core\src\org\apache\pivot\util\Version.java
Transmitting file data .done
Committing transaction...
Committed revision 1833933.
> 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)
