- This topic has 5 replies, 3 voices, and was last updated 16 years, 8 months ago by
Riyad Kalla.
-
AuthorPosts
-
Jerome JabsonMemberHello,
We are doing plug-in development and after updating from CVS, and setting our plug-in dependencies (via Java Build Path). Ran Manifest, which starts our App. To test we click: “Sample Action”. However, when we do, I get the following error:
java.lang.NoClassDefFoundError: Could not initialize class mezcalth.mcgsp.Main
at mcgplugin.actions.SampleAction.run(SampleAction.java:37)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:256)
at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:443)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
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:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
at org.eclipse.equinox.launcher.Main.main(Main.java:1148)The interesting thing here is that only the people using MyEclipse is having this problem. If I start regular Eclipse and do the same thing, it works fine! Here is my installation summary:
*** Date:
Friday, August 8, 2008 3:46:15 PM PDT** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_11*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 6.5.1 GA
Build id: 6.5.1-GA-20080715*** Eclipse details:
MyEclipse Enterprise WorkbenchVersion: 6.5.1 GA
Build id: 6.5.1-GA-20080715Eclipse Platform
Version: 3.3.3.r33x_r20080129-_19UEl7Ezk_gXF1kouft
Build id: M20080221-1800Eclipse RCP
Version: 3.3.3.r33x_r20080129-8y8eE9UEUWI6qujeED0xT7bc
Build id: M20080221-1800Eclipse Java Development Tools
Version: 3.3.2.r33x_r20080129-7o7jE7_EDhYDiyVEnjb1pFd7ZGD7
Build id: M20080221-1800Eclipse Plug-in Development Environment
Version: 3.3.3.r33x_r20080129-7N7M5DQVIA_6oJsEFkEL
Build id: M20080221-1800Eclipse Project SDK
Version: 3.3.3.r33x_r20080129-7M7J7LB-u3aphGW6o3_VmiVfGXWO
Build id: M20080221-1800Eclipse Graphical Editing Framework
Version: 3.3.2.v20080129
Build id: 20080221-1602Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Program Files\MyEclipse 6.5\eclipse\eclipse.exe
-name
Eclipse
–launcher.library
C:\Program Files\MyEclipse 6.5\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.3.R33x_v20080118\eclipse_1023.dll
-startup
C:\Program Files\MyEclipse 6.5\eclipse\plugins\org.eclipse.equinox.launcher_1.0.1.R33x_v20080118.jar
-exitdata
1304_78
-clean
-vm
C:\Program Files\MyEclipse 6.5\jre\bin\javaw.exeYour help in this manner is greatly appreciated.
Thank you,
Jerome
Loyal WaterMemberWas the project that your working with created using MyEclipse ? Or is it a non MyEclipse project?
Jerome JabsonMemberIt was created using regular Eclipse (RCP).
Riyad KallaMemberJerome,
Can you double-check the Java Build Path preferences between the two installs (ME: Not Working, E: Working) and just make sure all the same project refs and plugins refs are there? We don’t do anything special to change the base RCP tooling, so I wonder if some reference just got dorked somewhere.
Jerome JabsonMemberThe only difference in the Java Build Path is in the Plug-in Dependencies.
MyEclipse has the following listed:
browser.jar
htmltransferfix.jarIt appears that MyEclipse automatically adds these jar files automatically. I’m not sure if this is causing my problems. Can you shed some light on what these jar files are?
Riyad KallaMemberIIRC both of those are related to our visual HTML designer that utilizes customized Mozilla code to execute. You shouldn’t need them to run your app.
-
AuthorPosts