Trouble creating an SWT application visual class with 3.1 M6 [message #85408] |
Sat, 02 April 2005 16:54  |
Eclipse User |
|
|
|
Originally posted by: lesliesoftware.yahoo.com
I just downloaded 3.1M6 and, using the update manager, installed VE. I
guess my first question is should it work? I was able to create a Swing
visual class and that worked fine.
When I tried to craete an SWT application I recived an error saying
"Creation of element failed. See error log for more details." Attached
is the error log entry.
Thanks,
Ian
!ENTRY org.eclipse.jdt.ui 4 10001 2005-04-02 16:47:26.562
!MESSAGE Internal Error
!STACK 0
java.lang.reflect.InvocationTargetException
at org.eclipse.jface.operation.ModalContext.run(ModalContext.ja va:327)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java: 830)
at
org.eclipse.jdt.internal.ui.wizards.NewElementWizard.perform Finish(NewElementWizard.java:130)
at
org.eclipse.ve.internal.java.codegen.wizards.NewVisualClassC reationWizard.performFinish(NewVisualClassCreationWizard.jav a:407)
at
org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDi alog.java:676)
at
org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDi alog.java:349)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.jav a:556)
at
org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:89)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:842)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:2894)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2527)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:803 )
at org.eclipse.jface.window.Window.open(Window.java:781)
at org.eclipse.ui.actions.NewWizardAction.run(NewWizardAction.j ava:181)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:996 )
at
org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:538)
at
org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:488)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEven t(ActionContributionItem.java:400)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:842)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:2894)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2527)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1570)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1534)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:306)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:143)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:103)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:228)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:344)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:156)
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:585)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:315 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:268)
at org.eclipse.core.launcher.Main.run(Main.java:942)
at org.eclipse.core.launcher.Main.main(Main.java:926)
Caused by: java.lang.NullPointerException
at
org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspa th(JavaProject.java:2050)
at
org.eclipse.jdt.internal.core.ClasspathEntry.validateClasspa th(ClasspathEntry.java:1101)
at
org.eclipse.jdt.internal.core.SetClasspathOperation.verify(S etClasspathOperation.java:820)
at
org.eclipse.jdt.internal.core.JavaModelOperation.runOperatio n(JavaModelOperation.java:760)
at
org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(Ja vaProject.java:2739)
at
org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(Ja vaProject.java:2755)
at
org.eclipse.ve.internal.java.codegen.wizards.NewVisualClassC reationWizard.verifyProjectClassPath(NewVisualClassCreationW izard.java:345)
at
org.eclipse.ve.internal.java.codegen.wizards.NewVisualClassC reationWizard.finishPage(NewVisualClassCreationWizard.java:3 06)
at
org.eclipse.jdt.internal.ui.wizards.NewElementWizard$2.run(N ewElementWizard.java:114)
at
org.eclipse.jdt.internal.core.BatchOperation.executeOperatio n(BatchOperation.java:34)
at
org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaMod elOperation.java:710)
at org.eclipse.core.internal.resources.Workspace.run(Workspace. java:1714)
at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:3665)
at
org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter .run(WorkbenchRunnableAdapter.java:87)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:113)
Root exception:
java.lang.NullPointerException
at
org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspa th(JavaProject.java:2050)
at
org.eclipse.jdt.internal.core.ClasspathEntry.validateClasspa th(ClasspathEntry.java:1101)
at
org.eclipse.jdt.internal.core.SetClasspathOperation.verify(S etClasspathOperation.java:820)
at
org.eclipse.jdt.internal.core.JavaModelOperation.runOperatio n(JavaModelOperation.java:760)
at
org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(Ja vaProject.java:2739)
at
org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(Ja vaProject.java:2755)
at
org.eclipse.ve.internal.java.codegen.wizards.NewVisualClassC reationWizard.verifyProjectClassPath(NewVisualClassCreationW izard.java:345)
at
org.eclipse.ve.internal.java.codegen.wizards.NewVisualClassC reationWizard.finishPage(NewVisualClassCreationWizard.java:3 06)
at
org.eclipse.jdt.internal.ui.wizards.NewElementWizard$2.run(N ewElementWizard.java:114)
at
org.eclipse.jdt.internal.core.BatchOperation.executeOperatio n(BatchOperation.java:34)
at
org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaMod elOperation.java:710)
at org.eclipse.core.internal.resources.Workspace.run(Workspace. java:1714)
at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:3665)
at
org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter .run(WorkbenchRunnableAdapter.java:87)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:113)
|
|
|
|
|
|
|
Re: Trouble creating an SWT application visual class with 3.1 M6 [message #85807 is a reply to message #85537] |
Wed, 06 April 2005 11:18  |
Eclipse User |
|
|
|
We are trying to get a M6 based build going...
M6 has move everything in a plugin to be a single .jar, removed some API from M5 (not sure if to call them APIs, as they
were not in 3.0.x), and changed the build process.... This have thrown a few wrenches to VE M1 timing... from building
correctly, to launch the target VM with proper access to the swt .dll (which is not loose anymore, it is inside the swt
plugin's jar). As a matter of fact, the (Eclipse) launch SWT application does not work in M6 for the same reason.
Moving everything into a single .jar is a good thing overall for maintenance/deployment/performance/signature-signing
etc.; but it brings many skeletons out :-(
|
|
|
|
|
|
Re: Trouble creating an SWT application visual class with 3.1 M6 [message #606238 is a reply to message #85471] |
Mon, 04 April 2005 13:51  |
Eclipse User |
|
|
|
Hello,
Visual Editor 1.0.2 works with eclipse 3.1M4, but no newer milestone of
eclipse (3.1M5, 3.1M6).
For me, the Java 5 support in M4 is sufficient. I only have problems with
static imports (text completion throws NullPointerException, when a static
import is used).
I am using the following packages:
- eclipse-SDK-3.1M4-win32.zip
- emf-sdo-runtime-2.0.1.zip
- GEF-runtime-3.0.1.zip
- VE-runtime-1.0.2.zip
Kind regards
Stefan
|
|
|
Re: Trouble creating an SWT application visual class with 3.1 M6 [message #606278 is a reply to message #85537] |
Wed, 06 April 2005 11:18  |
Eclipse User |
|
|
|
We are trying to get a M6 based build going...
M6 has move everything in a plugin to be a single .jar, removed some API from M5 (not sure if to call them APIs, as they
were not in 3.0.x), and changed the build process.... This have thrown a few wrenches to VE M1 timing... from building
correctly, to launch the target VM with proper access to the swt .dll (which is not loose anymore, it is inside the swt
plugin's jar). As a matter of fact, the (Eclipse) launch SWT application does not work in M6 for the same reason.
Moving everything into a single .jar is a good thing overall for maintenance/deployment/performance/signature-signing
etc.; but it brings many skeletons out :-(
|
|
|
Powered by
FUDForum. Page generated in 0.05549 seconds