[Xena-devel] [ xena-Feature Requests-3385976 ] plugin version numbers should not have build in master

[SourceForge.net <no...@so...>]

Feature Requests item #3385976, was opened at 2011-08-04 10:53
Message generated for change (Comment added) made by terryoneill
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=577092&aid=3385976&group_id=85722

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Plugins
Group: None
Status: Open
Resolution: None
Priority: 6
Private: No
Submitted By: Terry O'Neill (terryoneill)
>Assigned to: Terry O'Neill (terryoneill)
Summary: plugin version numbers should not have build in master

Initial Comment:
The version numbers used in plugins currently are of the form:

<major>.<minor>.<increment>b<build number>

For example:
1.2.5b2

Build numbers should only be present in work under development and should not be present in stable releases on the master branch.  Currently the build number increments with each build so any user checking out the master branch will have the plugin version changed by the build number incrementing each time they build it.

----------------------------------------------------------------------

>Comment By: Terry O'Neill (terryoneill)
Date: 2011-08-31 17:30

Message:
Prepared and tested.

Made a change to add a "Release" boolean attribute to the jreleaseinfo
section of the build.xml and use this to determine whether to show the
build number or not (this is built into the JReleaseInfo class run through
ant).  Currently set to false but will change to true for the release.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=577092&aid=3385976&group_id=85722