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 73798 - Platform settings not reset after removing module from suite
Summary: Platform settings not reset after removing module from suite
Status: RESOLVED WONTFIX
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 5.x
Hardware: All All
: P4 blocker (vote)
Assignee: rmichalsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-21 10:13 UTC by pzajac
Modified: 2009-12-21 05:14 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 pzajac 2006-03-21 10:13:18 UTC 
[200608201800]
For example create PaintApp tutorial from example. Remove Paint project from
PaintApp suite. There are the same setting in platform.properties of Paint
module like in PaintApp suite. It is better to not copy
disabled.modules
enabled.clusters
disabled.clusters 
preperties to platfrom.properties during removing module from module suite.
Comment 1 Martin Krauskopf 2008-02-07 17:50:52 UTC 
I'm not working on APISupport anymore. Reassigning to owner of the component, so
the issue is not 'forgotten' forever.
Comment 2 Jesse Glick 2008-06-19 22:16:34 UTC 
Should not copy properties that are meaningless to standalone modules. Only need copy NB & Java platform names.
Comment 3 rmichalsky 2008-11-24 15:05:00 UTC 
Not into 7.0 or next release. Feel free to reopen if more important than it seems.
Comment 4 rmichalsky 2008-11-24 15:15:09 UTC 
A mistake, sorry.
Comment 5 Quality Engineering 2009-12-21 05:14:07 UTC 
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. 

We apologize for any inconvenience.


Thank you.
The NetBeans Team