| java.lang.NoClassDefFoundError with new eclipse 3.4 M7 [message #256569] |
Fri, 16 May 2008 20:14  |
Eclipse User |
|
|
|
Originally posted by: mansour.own.net
Everytime, I upgrade to a new release of eclipse I end up regretting it,
and worst I never learn. May be it's due to the hope that what is next,
is better, which eventually ends up with newer and bigger disappointment.
AspectJ files do not open in the editor. In fact they do not open at
all. And I can not run any existing class. I wrote this simple class
just to test, and got the same results.
============================================================ ======
public class TEST {
public static void main(String[] args) {
System.out.print("HELLO");
}
}
Exception in thread "main" java.lang.NoClassDefFoundError: TEST
============================================================ ======
Here's the error for aspectj (1.6.0):
java.lang.NullPointerException
at org.eclipse.jdt.ui.text.JavaTextTools.<init>(JavaTextTools.java:159)
at org.eclipse.jdt.ui.text.JavaTextTools.<init>(JavaTextTools.java:105)
at
org.eclipse.ajdt.internal.ui.editor.AspectJTextTools.<init>(AspectJTextTools.java:32)
at
org.eclipse.ajdt.internal.ui.editor.AspectJEditor.initialize Editor(AspectJEditor.java:497)
at
org.eclipse.ui.texteditor.AbstractDecoratedTextEditor.<init >(AbstractDecoratedTextEditor.java:294)
at
org.eclipse.jdt.internal.ui.javaeditor.JavaEditor.<init>(JavaEditor.java:239)
at
org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor . <init>(CompilationUnitEditor.java:1025)
at
org.eclipse.ajdt.internal.ui.editor.AspectJEditor.<init>(AspectJEditor.java:102)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Nativ e Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(Native ConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(De legatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:5 13)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at
org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI .createExecutableExtension(RegistryStrategyOSGI.java:170)
at
org.eclipse.core.internal.registry.ExtensionRegistry.createE xecutableExtension(ExtensionRegistry.java:863)
at
org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:243)
at
org.eclipse.core.internal.registry.ConfigurationElementHandl e.createExecutableExtension(ConfigurationElementHandle.java: 51)
at
org.eclipse.ui.internal.WorkbenchPlugin.createExtension(Work benchPlugin.java:260)
at
org.eclipse.ui.internal.registry.EditorDescriptor.createEdit or(EditorDescriptor.java:233)
at org.eclipse.ui.internal.EditorManager.createPart(EditorManag er.java:846)
at
org.eclipse.ui.internal.EditorReference.createPartHelper(Edi torReference.java:606)
at
org.eclipse.ui.internal.EditorReference.createPart(EditorRef erence.java:428)
at
org.eclipse.ui.internal.WorkbenchPartReference.getPart(Workb enchPartReference.java:594)
at
org.eclipse.ui.internal.EditorReference.getEditor(EditorRefe rence.java:266)
at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched( WorkbenchPage.java:2784)
at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(Workben chPage.java:2693)
at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPag e.java:2685)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.j ava:2637)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:67)
at
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPa ge.java:2632)
at
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPa ge.java:2616)
at
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPa ge.java:2607)
at
org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInE ditor(EditorUtility.java:331)
at
org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInE ditor(EditorUtility.java:194)
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:22 8)
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:20 7)
at
org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchR un(SelectionDispatchAction.java:274)
at
org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(Selec tionDispatchAction.java:250)
at
org.eclipse.jdt.internal.ui.navigator.OpenAndExpand.run(Open AndExpand.java:50)
at org.eclipse.ui.actions.RetargetAction.run(RetargetAction.jav a:221)
at
org.eclipse.ui.internal.navigator.CommonNavigatorManager$3.o pen(CommonNavigatorManager.java:184)
at
org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredV iewer.java:820)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.runtime.Platform.run(Platform.java:880)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:17 5)
at
org.eclipse.jface.viewers.StructuredViewer.fireOpen(Structur edViewer.java:818)
at
org.eclipse.jface.viewers.StructuredViewer.handleOpen(Struct uredViewer.java:1079)
at org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewe r.java:348)
at
org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(Stru cturedViewer.java:1183)
at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrate gy.java:263)
at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.ja va:257)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrate gy.java:297)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1154)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3398)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3030)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2394)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2358)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 10)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:494)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:489)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:112)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
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(EclipseS tarter.java:379)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Can anyone suggest something?
|
|
|
|
| Re: java.lang.NoClassDefFoundError with new eclipse 3.4 M7 [message #256592 is a reply to message #256569] |
Sat, 17 May 2008 02:45  |
| Eclipse User |
|
|
|
Mansour wrote:
> Everytime, I upgrade to a new release of eclipse I end up regretting it,
> and worst I never learn. May be it's due to the hope that what is next,
> is better, which eventually ends up with newer and bigger disappointment.
A motivation story for you:
With the 3.4 series, for the first time I tried to stay (half) bloody edge with
upgrading to the latest milestone as soon as it was available. M5 to M6 was
really a pain, the p2 system didn't solve any problems with update manager,
things got worse, I lost an entire day to get my setup running. So I really
hesitated to go from M6 to M7, but I did it - because I was courious. M7 is a
positive surprise to me. Everything works as I expect and I did the setup in
less than an hour. And Ed is really saying the right thing. Because _you_ get
that error and report it to the aj people, they get the chance to fix it.
Felix
|
|
|
| Re: java.lang.NoClassDefFoundError with new eclipse 3.4 M7 [message #256656 is a reply to message #256592] |
Sat, 17 May 2008 20:49 |
| Eclipse User |
|
|
|
Originally posted by: mansour.own.net
Thank you for the motivation story. I uninstalled AspectJ Dev Tools and
things went fine. I will into this issue later. Probably I did something
wrong.
Felix Dorner wrote:
> Mansour wrote:
>> Everytime, I upgrade to a new release of eclipse I end up regretting
>> it, and worst I never learn. May be it's due to the hope that what is
>> next, is better, which eventually ends up with newer and bigger
>> disappointment.
>
> A motivation story for you:
> With the 3.4 series, for the first time I tried to stay (half) bloody
> edge with upgrading to the latest milestone as soon as it was available.
> M5 to M6 was really a pain, the p2 system didn't solve any problems with
> update manager, things got worse, I lost an entire day to get my setup
> running. So I really hesitated to go from M6 to M7, but I did it -
> because I was courious. M7 is a positive surprise to me. Everything
> works as I expect and I did the setup in less than an hour. And Ed is
> really saying the right thing. Because _you_ get that error and report
> it to the aj people, they get the chance to fix it.
>
> Felix
|
|
|
| Re: java.lang.NoClassDefFoundError with new eclipse 3.4 M7 [message #256660 is a reply to message #256592] |
Sat, 17 May 2008 20:49 |
| Eclipse User |
|
|
|
Originally posted by: mansour.own.net
Thank you for the motivation story. I uninstalled AspectJ Dev Tools and
things went fine. I will into this issue later. Probably I did something
wrong.
Felix Dorner wrote:
> Mansour wrote:
>> Everytime, I upgrade to a new release of eclipse I end up regretting
>> it, and worst I never learn. May be it's due to the hope that what is
>> next, is better, which eventually ends up with newer and bigger
>> disappointment.
>
> A motivation story for you:
> With the 3.4 series, for the first time I tried to stay (half) bloody
> edge with upgrading to the latest milestone as soon as it was available.
> M5 to M6 was really a pain, the p2 system didn't solve any problems with
> update manager, things got worse, I lost an entire day to get my setup
> running. So I really hesitated to go from M6 to M7, but I did it -
> because I was courious. M7 is a positive surprise to me. Everything
> works as I expect and I did the setup in less than an hour. And Ed is
> really saying the right thing. Because _you_ get that error and report
> it to the aj people, they get the chance to fix it.
>
> Felix
|
|
|
Powered by
FUDForum. Page generated in 0.07670 seconds
Home