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 91640

Summary:	Add shortcut to Deploy action
Product:	javame	Reporter:	_ gtzabari <gtzabari>
Component:	Build System	Assignee:	Petr Suchomel <psuchomel>
Status:	NEW ---
Severity:	blocker	CC:	olangr
Priority:	P3
Version:	5.x
Hardware:	All
OS:	All
Issue Type:	ENHANCEMENT	Exception Reporter:

Description _ gtzabari 2006-12-29 22:08:39 UTC

There seems to be some confusion or a bug in the way MIDlet-Jar-Size is
generated. When I hit F11 "Build main project" I was actually expecting Netbeans
to deploy it. In fact, building the project and deploying it are two completely
different actions. So the first problem I am reporting is that there doesn't
seem to be a shortcut key for the deploy action.

  The second problem is that the JAD file in the "dist" directory contains an
incorrect MIDlet-Jar-Size value if F11 is used to build the project. The value
only becomes correct once Deploy is invoked.

  So the second issue is that Netbeans probably shouldn't generate a JAD file if
it isn't usable because this leads to confusion. Personally I expect F11 to
generate a valid JAD file with the correct MIDlet-Jar-Size so I can double
clicks on the JAD file and have it run inside an emulator. Right now this does
not work.

Comment 1 Martin Ryzl 2007-01-02 10:45:03 UTC

I agree that it would be useful to have a shortcut for Deploy action however I
can't reproduce the issue with wrong jar size.
Whenever I hit F11, I see message like this in the ouput tab and jar size in the
jad file is correct. Do you have more details that would help us to reproduce
the problem?:

Building jar: C:\Documents and
Settings\user\MobileApplication1\dist\MobileApplication1.jar
Updating application descriptor: C:\Documents and
Settings\user\MobileApplication1\dist\MobileApplication1.jad
Generated "C:\Documents and
Settings\user\MobileApplication1\dist\MobileApplication1.jar" is 26761 bytes.
post-jar:
BUILD SUCCESSFUL (total time: 1 second)

Comment 2 Adam Sotona 2007-05-21 16:42:51 UTC

As I am also not able to reproduce the invalid Jar size I am transfering this
defect to an enhacement about the missing keyword (first part of the problem).