Community
Participate
Working Groups
nightly 0429 1. Cntrl-3 brings up the universal chooser 2. type "new cvs", you will see the command to open a new CVS repo 3. choose that You will get a class cast exception. Doesn't matter if the CVS repo view is open or not. Top of stack looks like: java.lang.ClassCastException: org.eclipse.team.internal.ccvs.ui.wizards.NewLocationWizard at org.eclipse.ui.internal.actions.NewWizardShortcutAction.run(NewWizardShortcutAction.java:87) at org.eclipse.ui.internal.quickaccess.WizardElement.execute(WizardElement.java:41) at org.eclipse.ui.internal.quickaccess.QuickAccessDialog.handleElementSelected(QuickAccessDialog.java:616) at org.eclipse.ui.internal.quickaccess.QuickAccessDialog$5.widgetDefaultSelected(QuickAccessDialog.java:264)
NewLocationWizard does not implement the marker interface INewWizard as required per extension point schema.
I have a problem here. It may be the case that the schema states that the wizard should implement INewWizard but it doesn't enforce it (i.e. there is no warning or error in my plug-in.xml) and the New Wizard Wizard doesn't require it (i.e. it works from the New Wizard). I think the workbench needs to enforce the use of INewWizard consistently (i.e. if should either work in both places or fail in both places). I will fix this is CVS and then forward the bug to Platform/UI.
I've released the fix to HEAD. Reassigning to Boris to respond to my previous comments.
(In reply to comment #2) > I have a problem here. It may be the case that the schema states that the > wizard should implement INewWizard but it doesn't enforce it (i.e. there is no > warning or error in my plug-in.xml) This is odd because we do spec it in the newWizards.exsd file. <attribute name="class" type="string" use="required"> <annotation> <documentation> a fully qualified name of the Java class implementing <samp>org.eclipse.ui.INewWizard</samp>. </documentation> <appinfo> <meta.attribute kind="java" basedOn="org.eclipse.jface.wizard.Wizard:org.eclipse.ui.INewWizard"/> </appinfo> </annotation> </attribute> > and the New Wizard Wizard doesn't require > it (i.e. it works from the New Wizard). I think the workbench needs to enforce > the use of INewWizard consistently (i.e. if should either work in both places > or fail in both places). This seems to be because the dialog merely casts to IWorkbenchWizard whereas Ctrl+3 casts to INewWizard.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
