Also, changes get reflected in your App’s platform.properties file. So, if you want to avoid using GUI for removing a cluster, not specific modules within that cluster, and tweak it directly in the file.
Continue reading...
apisupport1, gsf1, harness, ide10, java2, nb6.5, platform9, profiler3, websvccommon1
By default, your application’s platform.properties file stored under nbproject and displayed as NetBeans Platform Config in Logical View, has contents..
nbplatform.active=default
That’s the only property you have. Now, suppose I want to remove gsf1 cluster from the above list, add the following property-
enabled.clusters=\
apisupport,\
harness,\
ide,\
java,\
nb,\
platform,\
profiler,\
websvccommon
So, as you can see the properties file doesn’t show version of the clusters (ordered alphabetically always), so its version independent as well. This is what you see when you remove gsf1 cluster using Project Properties Wizard, and rest are meant to be enabled by the Application you are using.
Now, if I want to restore gsf1, and remove websvccommon1, then you need to just tweak it as follows-
enabled.clusters=\
apisupport,\
gsf,\
harness,\
ide,\
java,\
nb,\
platform,\
profiler
If you remove some specific modules from a particular cluster, then following properties are added into the properties file-
disabled.modules=\
{codename.base.of.modules}
enabled.clusters=\
apisupport,\
gsf,\
harness,\
ide,\
java,\
nb,\
platform,\
profiler,\
websvccommon
Here you would see that when I disable (Please use GUI Wizard to disable) some modules from (suppose) java2 cluster, their Code Name Base would be added into the disabled.modules property. Also, you are required to add enabled.clusters property, with all clusters included.
enabled.clusters=
disabled.modules=\
A
enabled.clusters=\
B,\
C,\
D
However, if you want to enable some of the modules disabled using Wizard, then of course you may use the tweaks shown above to do the trick.
Hope this helps..