[
https://issues.apache.org/jira/browse/PIVOT-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518439#comment-16518439
]
Sandro Martini commented on PIVOT-1035:
---------------------------------------
Sorry one last comment, on the value set in the "Implementation-Version", are
we sure that consumers of generated jar like a version string written that way
? Or maybe if if makes sense to move that timestmp in another metadata field
there ?
For example in [Setting Package Version
Information|https://docs.oracle.com/javase/tutorial/deployment/jar/packageman.html]
I see that there are other standard fields like "Specification-Version" that
could be set to main release (2.1.0) and maybe "Implementation-Version" with
the build/revision ... what do you think ?
> 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)
