[
https://issues.apache.org/jira/browse/PIVOT-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518364#comment-16518364
]
Roger Whitcomb commented on PIVOT-1035:
---------------------------------------
Ciao [~smartini], right now the build number is local (in a "build.number"
file). This could be checked into svn to make it a global number.... I don't
know how to use the commit id/hash for that purpose, but that's not a bad idea.
Have you seen that done in other places? Of course, that works for a CI
build, where you (presumably) have one build per commit. Doesn't work so well
for multiple, interim builds without intervening changes, though. That's why I
say I don't know how best to make it work, but it seems like *something* is
better than just having the number be "00" all the time.
> 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)
