[
https://issues.apache.org/jira/browse/PIVOT-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518393#comment-16518393
]
Roger Whitcomb commented on PIVOT-1035:
---------------------------------------
Changed to use a date format of "YYYYDDDHHmm" for the build number now (looks a
bit ugly and too long, but it is definitely unique and always increasing).
Implementation-Title : Apache Pivot Core
Implementation-Version : 2.1.0_20181711037
Sending build.xml
Transmitting file data .done
Committing transaction...
Committed revision 1833931.
What do you think? Too ugly?
> 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)
