This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Currently, the Application Version Counter (General category in Properties) bumps up the version number after each build. I build frequently, and I might make hundreds of builds before incrementing a minor or major version number, where: x.y.z is x = major version number (new major featureset) y = minor version number (new minor features) z = build number (mostly used to identify a particular build) I would happily use the Application Version Number as a build counter. However, in the present implementation, every 100 versions, the Application Version Counter increments the minor version number and the build number is reset to zero, as in: 0.0.98 -> 0.0.99 -> 0.1.0 This is not very useful. What would be useful would be the addition of a checkbox "Append Build Counter", which if checked, would append a build number to the Application Version Number. There would also be a text field called "Build Separator" which one might set to ".", "_", or "-" depending on their preference. Finally there would be a text area "Build Counter" containing the actual version of the build counter. If the build counter were enabled, the Application Version Counter would be disabled (they are not compatible because they work differently." Finally, "Current Application Version" would display the "Application Version Number" with the "Build Counter" appended as it would appear in the JAD file or a version attribute. So, if - Application Version Number is set to 0.1 - Append Build Counter is checked - Build Separator is "." - Build Counter is 1198 (presumably, the developer had created 1198 builds) the Current Application Version would be 0.1.1198 For each build, Build Counter simply increments, producing consecutive application versions: 0.1.1198 -> 0.1.1199 -> 0.1.1200 There is no rollover of the base Application Version Number. Similarly if the Application Version Number were 0.8.12, the Current Application Version would be 0.8.12.1198. If someone decided that it was time to increment the major or minor version numbers, they would simply go into Properties and set these manually, and presumably set the build counter back to 0, again manually.
Reassigning to java.
I've noticed that at least one emulator platform - Motorola iDEN - and possible also their phones - does not like (and fails to install) MIDlets with version tags that might be formatted as I have suggested here (ie, 0.5.1282 where 1282 is the build number.) Still, I think the build number capability would be valuable, and perhaps there should be an option to store it as a separate JAD attribute, perhaps as a variable for which the actual build number can be substituted at build time into the JAD attribute of the developer's choosing.