Unable to run scriptsEPIC 3.1.2 Eclipse 3.0.2

ronw_000 wrote on Sat Sep 24 22:34:23 MEST 2005:

I installed EPIC 3.1.2 (was previously using 3.1.1) using update site. 
I am running Eclipse 3.0.2.  Now when I try to run a perl script I receive
the error:

"Exception occurred during launch

 Reason:
 Error within Debug UI:"

Same result no matter how run is selected (menu, toolbar) or which run option
is selected.

Does 3.1.2 require Eclipse 3.1?

jploski wrote on Sat Sep 24 23:57:20 MEST 2005:

Yes, "testing 0.3.12" apparently requires Eclipse 3.1. I posted a bug report
to cover this topic. Please confirm that you are getting the same exception
(see the Error Log view):

https://sourceforge.net/tracker/index.php?func=detail&aid=1303529&group_id=75859&atid=545274

ronw_000 wrote on Sun Sep 25 05:51:10 MEST 2005:

I am running Eclipse 3.0.2 on Win32 (XP).  I also am testing 3.1.2 with
Eclipse 3.1 (so far-so good).  My 3.1.2/Eclipse 2.0.2 error message is slightly
different than yours.  See below:

eclipse.buildId=M200409161125

java.lang.reflect.InvocationTargetException
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:284)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:397)
at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:251)
at org.eclipse.ui.internal.progress.ProgressManager$3.run(ProgressManager.java:837)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:871)
at org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:847)
at org.eclipse.debug.internal.ui.DebugUIPlugin.launchInForeground(DebugUIPlugin.java:872)
at org.eclipse.debug.ui.DebugUITools.launch(DebugUITools.java:520)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.handleLaunchPressed(LaunchConfigurationsDialog.java:1076)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.buttonPressed(LaunchConfigurationsDialog.java:284)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:506)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:796)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2773)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2432)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:668)
at org.eclipse.jface.window.Window.open(Window.java:648)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:419)
at org.eclipse.debug.ui.DebugUITools$1.run(DebugUITools.java:381)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:385)
at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:327)
at org.eclipse.debug.ui.actions.OpenLaunchDialogAction.run(OpenLaunchDialogAction.java:80)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:881)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:915)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:866)
at org.eclipse.jface.action.ActionContributionItem$7.handleEvent(ActionContributionItem.java:785)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:796)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2773)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2432)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1377)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1348)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:254)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:96)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:335)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129)
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.core.launcher.Main.basicRun(Main.java:185)
at org.eclipse.core.launcher.Main.run(Main.java:704)
at org.eclipse.core.launcher.Main.main(Main.java:688)
Caused by: java.lang.NoClassDefFoundError: org/eclipse/debug/core/model/DebugElement
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at org.eclipse.osgi.framework.internal.defaultadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:298)
at org.eclipse.core.runtime.adaptor.EclipseClassLoader.defineClass(EclipseClassLoader.java:223)
at org.eclipse.osgi.framework.internal.defaultadaptor.DefaultClassLoader.findClassImpl(DefaultClassLoader.java:281)
at org.eclipse.osgi.framework.internal.defaultadaptor.DefaultClassLoader.findClass(DefaultClassLoader.java:172)
at org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.findLocalClass(AbstractClassLoader.java:220)
at org.eclipse.core.runtime.adaptor.EclipseClassLoader.basicFindLocalClass(EclipseClassLoader.java:135)
at org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLocalClass(EclipseClassLoader.java:59)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:371)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:402)
at org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(AbstractClassLoader.java:93)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
at java.lang.Class.getConstructor0(Unknown Source)
at java.lang.Class.newInstance0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:141)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:124)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:113)
at org.eclipse.debug.internal.core.LaunchConfigurationType.getDelegate(LaunchConfigurationType.java:231)
at org.eclipse.debug.internal.core.LaunchConfiguration.getDelegate(LaunchConfiguration.java:360)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:514)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:788)
at org.eclipse.debug.internal.ui.DebugUIPlugin$5.run(DebugUIPlugin.java:865)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
Root exception:
java.lang.NoClassDefFoundError: org/eclipse/debug/core/model/DebugElement
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at org.eclipse.osgi.framework.internal.defaultadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:298)
at org.eclipse.core.runtime.adaptor.EclipseClassLoader.defineClass(EclipseClassLoader.java:223)
at org.eclipse.osgi.framework.internal.defaultadaptor.DefaultClassLoader.findClassImpl(DefaultClassLoader.java:281)
at org.eclipse.osgi.framework.internal.defaultadaptor.DefaultClassLoader.findClass(DefaultClassLoader.java:172)
at org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.findLocalClass(AbstractClassLoader.java:220)
at org.eclipse.core.runtime.adaptor.EclipseClassLoader.basicFindLocalClass(EclipseClassLoader.java:135)
at org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLocalClass(EclipseClassLoader.java:59)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:371)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:402)
at org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(AbstractClassLoader.java:93)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
at java.lang.Class.getConstructor0(Unknown Source)
at java.lang.Class.newInstance0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:141)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:124)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:113)
at org.eclipse.debug.internal.core.LaunchConfigurationType.getDelegate(LaunchConfigurationType.java:231)
at org.eclipse.debug.internal.core.LaunchConfiguration.getDelegate(LaunchConfiguration.java:360)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:514)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:788)
at org.eclipse.debug.internal.ui.DebugUIPlugin$5.run(DebugUIPlugin.java:865)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)

jploski wrote on Sun Sep 25 12:01:06 MEST 2005:

Thanks for confirmation. This appears to be the same problem: the stack
traces of your RootException and my reported exception are equal starting
from org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:788).

marcbernst wrote on Sun Jan  8 05:47:43 CET 2006:

At the risk of sounding like a windows 'reboot admin' for eclipse,

get rid of your workspace, recreate your project (hopefully your settings
are ok), make sure you are using padwalker.pm from epic on sourceforge -
not the cpan version.

I assume you are using ActivePerl?

ronw_000 wrote on Thu Jan 12 08:11:25 CET 2006:

Yes, using EPIC Padwalker (for ActiveState Perl 5.8.1 or higher) with ActiveState
Perl 5.8.4 with both EPIC 3.11 debugger and EPIC 3.12 debugger.  Sorry I
didn't mention rebuilding the workspace it is SOP (Standard Operating Procedure)
for most Eclipse problems.  Have you been successful using EPIC 3.1.2 with
Eclipse 3.0.2 on ActiveState Perl 5.8.4 with the EPIC Padwalker for ActiveState
Perl 5.8.1 or higher?  What would you suggest as a next step?

jploski wrote on Thu Jan 12 19:26:38 CET 2006:

Upgrade to Eclipse 3.1? Is anything holding you back?

marcbernst wrote on Sat Jan 14 08:42:21 CET 2006:

Please enlighten me what 'you' mean by rebuilding a workspace. All I know
to do is delete it and start over. Also, can you explain to me how I resync
with a project when I return to epic. It is there to sync with but I see
no way to 'load' it.

jploski wrote on Sat Jan 14 12:45:48 CET 2006:

To "rebuild workspace", issue the command "Project/Clean..." on all projects
contained in it (before doing it, issue the command "Refresh" on all projects).
If autobuild is enabled, the building will then start automatically. If
not, you have to do "Project/Build All". Note that these steps are not EPIC-specific.

To import a project into workspace, use "New/Project..." and specify its
existing location on disk. If your project is already in the workspace (i.e.
visible in the Resources view) but desynchronised with disk because of external
edits, you can do "Refresh" from the context menu (this will also trigger
autobuild if enabled). These steps are not EPIC-specific either.

Note that you do not need to create a new workspace when upgrading from
3.0 to 3.1. With the -data command-line option to Eclipse you can specify
the workspace location on disk. However, once you start using the workspace
with 3.1 it is not advisable to also use it with 3.0.

ronw_000 wrote on Tue Jan 17 19:11:20 CET 2006:

I am using Eclipse 3.1/EPIC 3.12 as I stated in my post on the "Debugger
problems in Eclipse 3.1" thread.  I am quite happy with the combination.
The rest of my team is still on Eclipse 3.0.2 as several commercial plugins
we use on a daily basis are not compatible with Eclipse 3.1 yet. I suspect
the plugins will not be fully compatible with Eclipse 3.1 for some time.