Community
Participate
Working Groups
Adopters have the ability to hide actions / wizards in their products through the "capabilities" mechanism's, which give the ability to hide through the standard "new" -> "project" etc.. tree format... This mechanism fails for action bar's that are constructed in the Java EE perspective. A new extension point can enable adopters to register any new project wizard id they wish to hide. By default, no behavior will change.
Created attachment 209315 [details] patch This includes the new extension point, and extra check while building the Java EE Action bar used in the JavaEE perspective. The extension point grammar looks like this if for instance an adopter would like to filter the "static web project" action: <extension point="org.eclipse.jst.j2ee.ui.newjavaeeactionfilter"> <newjavaeewizardId filterwizard="org.eclipse.wst.web.ui.internal.wizards.SimpleWebProjectWizard"> </newjavaeewizardId> </extension>
Asking for review from Carl, and after I will submit to PMC because this is a new ext point
Created attachment 209337 [details] cleaned up patch Tweaked naming of a few methods - cleaned up api
Putting up for PMC review: 1) Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug" (requested by an adopter) please document it as such. An adopter product has implemented a wizard that replaces function from WTP, and would like to only highlight the adopter action in their product. Capabilities are used to perform 90% of this, but are not sufficient for hiding the drop-down action bar in the Java EE perspective. 2) Is there a work-around? If so, why do you believe the work-around is insufficient? No 3) How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? The fix effects UI(filtering menu items) - we have performed manual testing 4) Give a brief technical overview. Who has reviewed this fix? A new extension point is now available to enable adopters to register Wizard id's they wish to filter used in the Action bar. By default the menu will be unchanged 5) What is the risk associated with this fix? None
Committed to both R3_3_Maintenance and HEAD
