Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #252807 +++ Each project will provide basic capability/activity definitions to allow for their UI contributions to be hidden. These must be provided in a separate plugin/feature to facilitate inclusion/exclusion by consumers in product development.
done for EMF Compare
Done for EMFT Ecore Tools. I did the following to deliver capabilities to Galileo : 1) Created a new org.eclipse.emf.ecoretools.ui.capabilities plugin for Galileo only + a new org.eclipse.emf.ecoretools.ui.capabilities-feature feature but, it is not referenced yet. In the plugin, I only define a generic pattern for my capabilities : "org\.eclipse\.emf\.ecoretools/.*". 2) Added to the Galileo capabilities map file + add the org.eclipse.emf.ecoretools.ui.capabilities plugin to the galileo feature + add corresponding category bindings and default enablement in the galileo plugin. I am not really familiar with Capabilities, so I tried to basically adapt what has been done in others projects (such as EMF, EMF Compare or GEF). Hope I did not miss anything and the galileo build won't break because of me ...
Mint uses capabilities/activities; however, not in a separate plugin (will leave that for SR1 or next release).
MWE uses capabilities/activities.
Pretty much done.