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 62139 - deployment.number doesn't work in projects upgraded from 4.0 to 4.1
Summary: deployment.number doesn't work in projects upgraded from 4.0 to 4.1
Status: CLOSED WORKSFORME
Alias: None
Product: javame
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Adam Sotona
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-10 22:04 UTC by dcowing
Modified: 2006-10-23 16:41 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description dcowing 2005-08-10 22:04:44 UTC 
I have a mobile application I created in NB 4.0.  I upgraded to the project to
4.1.  When I attempted to use the new feature to auto-increment the
MIDlet-Version attribute with the ${deployment.number} it didn't work.  The
actual text "${deployment.number} is put in the jad and the manifest of the jar.

In purusing the project files (build-impl.xml?) in nbproject, I noticed that
several ant commands around deployment didn't exist in my upgraded project, but
do exist in new mobile applications that i create in NB4.1 (the auto-numbering
of builds worked with a freshly created project).
Comment 1 Milan Kubec 2005-08-17 08:27:40 UTC 
Mobility issue.
Comment 2 Adam Sotona 2005-08-18 14:00:22 UTC 
Your build-impl.xml has to be exactly the same for all upgraded projects as for
any new project because the scripts are automatically upgraded.

The upgrade may be cancelled if you did some manual modifications to the
build-impl.xml.

Try to delete the build-impl.xml and re-open the project - it should re-generate
the script and solve your problem.
Comment 3 Lukas Hasik 2006-01-17 13:57:44 UTC 
verifying all old issues