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 71146 - [50cat] Be able to control which configuration is included in Deploy All and which isn't
Summary: [50cat] Be able to control which configuration is included in Deploy All and ...
Status: CLOSED INVALID
Alias: None
Product: javame
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Martin Ryzl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-08 22:24 UTC by ieising
Modified: 2006-10-23 16:41 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 ieising 2006-01-08 22:24:39 UTC
[ JDK VERSION : 1.6 ]

Hi,

I've got many configurations for my MIDlet, a about 20% of them is just for debug purposes.
When I do a deploy all, I don't want these to be included in the target, so basically I would like to be able to set for each configuration whether it is a configuration that is deployed or not.
The other issue with this, is that the deployment counter is increased for these configurations as well, although I never really deploy them.

Iwan
Comment 1 Lukas Hasik 2006-01-09 08:43:07 UTC
there is Deployment method "<none>". 
set all configurations that you dont want deploy to <none>. 
Comment 2 ieising 2006-01-09 19:44:31 UTC
Hmmm, okay I didn't see that one. Stupid, stupid, stupid. Why didn't I take a
closer look. I've set the Default one to <none> and all that I don't want
deployed to use the Default settings.

If you want, you may close it as invalid. I stick with my other issue about the
config tree.

Iwan
Comment 3 Lukas Hasik 2006-01-10 10:29:17 UTC
closing as invalid.

This issue can be solved in existing enviroment.

Iwan, you aren't stupid. We should point it out when even you (experienced user)
didn't notice it. 
Keep the issues coming
Comment 4 ieising 2006-01-17 09:30:29 UTC
Yes, it is possible. Is it an idea to put on the deployment-page in the
project's properties a message stating that you can remove it from the
deployable configs list by setting it to <none>?
Comment 5 Lukas Hasik 2006-01-17 14:14:45 UTC
closing this issue

I created issue 71494 to get this message into next release. It's too late for 5.0