The "org.polarsys.capella.core.platform.sirius.ui.perspective" plugin defines a number of capabilities, but some of them are way too generic.
Capability "org.polarsys.capella.activities.capellaProjects" only binds the "new project wizard" :
<activityPatternBinding activityId="org.polarsys.capella.activities.capellaProjects" isEqualityPattern="true" pattern="org.polarsys.capella.core.platform.sirius.ui.project/capella.project.wizard"> </activityPatternBinding>
That is fine. However, the "org.polarsys.capella.activities.wizards" binds "all" wizards without making any distinction :
<activityPatternBinding pattern="org.polarsys.capella.core.*wizard.*" activityId="org.polarsys.capella.activities.wizards" />
This means that whatever you do with the "capella projects" capability, the wizard will never be disabled, because the "wizards" capability tells eclipse that it should be activated. Likewise, even if you disable the "libraries" capability, the "new capella library" wizard will still be there and allow us to create libraries.
As long as you don't disable the red "wizards" capability, disabling "Capella Projects" does nothing, disabling "libraries" will still show all library related wizards, disabling "Configuration projects" will still show the wizard to create them.
But disabling "wizards" means that we may disable critical parts of capella since "org.polarsys.capella.core.wizard." matches a lot of things all throughout the tool (trace manager, Logical Component Decomposition, allocation management... probably many others).
I believe that capability should be removed altogether.
The "org.polarsys.capella.core.platform.sirius.ui.perspective" plugin defines a number of capabilities, but some of them are way too generic.
Capability "org.polarsys.capella.activities.capellaProjects" only binds the "new project wizard" :
<activityPatternBinding activityId="org.polarsys.capella.activities.capellaProjects" isEqualityPattern="true" pattern="org.polarsys.capella.core.platform.sirius.ui.project/capella.project.wizard"> </activityPatternBinding>That is fine. However, the "org.polarsys.capella.activities.wizards" binds "all" wizards without making any distinction :
<activityPatternBinding pattern="org.polarsys.capella.core.*wizard.*" activityId="org.polarsys.capella.activities.wizards" />This means that whatever you do with the "capella projects" capability, the wizard will never be disabled, because the "wizards" capability tells eclipse that it should be activated. Likewise, even if you disable the "libraries" capability, the "new capella library" wizard will still be there and allow us to create libraries.
As long as you don't disable the red "wizards" capability, disabling "Capella Projects" does nothing, disabling "libraries" will still show all library related wizards, disabling "Configuration projects" will still show the wizard to create them.
But disabling "wizards" means that we may disable critical parts of capella since "org.polarsys.capella.core.wizard." matches a lot of things all throughout the tool (trace manager, Logical Component Decomposition, allocation management... probably many others).
I believe that capability should be removed altogether.