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.

Bug 67919 - [50cat] Automatic versening of Modules based on build numbers
Summary: [50cat] Automatic versening of Modules based on build numbers
Status: VERIFIED WONTFIX
Alias: None
Product: apisupport
Classification: Unclassified
Component: Harness (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-01 14:57 UTC by kalali
Modified: 2006-01-18 09:57 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kalali 2005-11-01 14:59:07 UTC
[ BUILD # : 20051013 ]
[ JDK VERSION : 1.5.0_03 ]

Automatic versening of Modules , as you know modules have version numbers
Is it possible to make those version to increases in each build ?
in the way that let users to determine some digits as LSN , then you increase IDE increase them
as it build the mdules ,
for example : 
Implementation version : 
1.0.0.XX in this case those XX could increase in each build .


profits :
1- you compete with Delphi build number and versioning
2-user know how much time he/she builds te module
3-installing will be easier on end systems , as update center will recognize updated module based on thies version number.
....
Comment 1 Jesse Glick 2005-11-02 02:23:24 UTC
We already include the date at least in the impl version (or build number
field); you can set ${buildnumber} to your choice of formats. Generally we do
not recommend automatic incrementing of version numbers with every build -
increment it manually when you actually have a new feature that you want to
publish. However if you wish to do such numbering yourself, you should be able
to do so in your own build.xml, e.g. by using standard Ant tasks to modify
manifest.mf periodically, or (more VCS-friendly) creating a separate
build/manifest-versioned.mf from your source manifest.mf and setting
${manifest.mf} to that so the standard jar target picks it up.
Comment 2 kalali 2006-01-18 09:57:43 UTC
verified.