Adding a PCMSolver configuration fails on file extension filter

Description

When creating a new PCMSolver configuration the error below occurs. This is on the nightly build obtained 28th July 2011 through the Eclipse update mechanism.

Cannot test effect on existing PCMSolver configurations, because none are existant.

Goal was to use the LQNS.

– Eclipse error info –

eclipse.buildId=unknown
java.version=1.6.0_24
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.epp.package.modeling.product
Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.modeling.product

Error
Thu Jul 28 16:37:22 CEST 2011
Problems occurred when invoking code from plug-in: "org.eclipse.jface".

java.lang.NoSuchMethodError: de.uka.ipd.sdq.workflow.launchconfig.tabs.TabHelper.validateFilenameExtension(Ljava/lang/String;[Ljava/lang/String;)Z
at de.uka.ipd.sdq.workflow.pcm.runconfig.FileNamesInputTab.isValid(FileNamesInputTab.java:183)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.canLaunch(LaunchConfigurationTabGroupViewer.java:1071)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$1.run(LaunchConfigurationsDialog.java:511)
at org.eclipse.debug.ui.AbstractDebugView.doubleClick(AbstractDebugView.java:729)
at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:821)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.runtime.Platform.run(Platform.java:888)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:819)
at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1419)
at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1195)
at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:238)
at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:235)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:296)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3910)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3503)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1065)
at org.eclipse.debug.ui.DebugUITools$1.run(DebugUITools.java:398)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:406)
at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:340)
at org.eclipse.debug.ui.actions.OpenLaunchDialogAction.run(OpenLaunchDialogAction.java:81)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3910)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3503)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)

Environment

Operating System: Windows 7
Platform: PC

Activity

Show:
Thijmen de Gooijer
July 29, 2011, 8:54 AM

(In reply to comment #1)
> The PCM build has been split into several builds in the last weeks. Please try
> the following:
> - check all PCM plugins are recent:
> – Go to Help -> About Eclipse -> Installation details -> Plug-ins
> – Sort the plug-ins by plug-in ID
> – check whether the de.uka.ipd.sdq.workflow plug-ins all have the same build
> date (or very close) as the main PCM plug-ins, such as de.uka.ipd.sdq.pcm
> If not, you have an older base Eclipse installation and need to add the build
> site of the Workflow Engine to your Update Site. See
> http://sdqweb.ipd.kit.edu/wiki/PCM_3.3#Installation_through_update_site_.28Galileo.29
> for information how to add the workflow update site.
> Afterwards, the plug-in build dates should be identical or very close.
> If you already have plugins with the same date, let me know.

Yes, didn't have these. Problem resolved.

User known
July 28, 2011, 4:53 PM

The PCM build has been split into several builds in the last weeks. Please try the following:

  • check all PCM plugins are recent:

    • Go to Help -> About Eclipse -> Installation details -> Plug-ins

    • Sort the plug-ins by plug-in ID

    • check whether the de.uka.ipd.sdq.workflow plug-ins all have the same build date (or very close) as the main PCM plug-ins, such as de.uka.ipd.sdq.pcm

If not, you have an older base Eclipse installation and need to add the build site of the Workflow Engine to your Update Site. See http://sdqweb.ipd.kit.edu/wiki/PCM_3.3#Installation_through_update_site_.28Galileo.29 for information how to add the workflow update site.

Afterwards, the plug-in build dates should be identical or very close.

If you already have plugins with the same date, let me know.

Incomplete

Assignee

Former user

Reporter

Thijmen de Gooijer

Labels

None

Requirement Category

None

External issue URL

Severity

normal

Priority

P5

Status Whiteboard

None

External issue ID

745

Components

Affects versions

Priority