search

gongdaowen / run-jetty-run

Automatically exported from code.google.com/p/run-jetty-run
0 stars 0 forks source link

Exception while trying to configure the launcher #141

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.Go to Debug Run configurations...
2.Create a Jetty Webapp launch configuration
3.See exception "Items models shouldn't be null".  Update LCD.
4.The dialog isn't shown

This leads the plugin to unusable.

Detailed exception:
java.lang.IllegalStateException: Items model shouldn't be null
    at runjettyrun.tabs.AbstractClasspathTab.isValid(AbstractClasspathTab.java:669)
    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.refresh(LaunchConfigurationTabGroupViewer.java:463)
    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.updateButtons(LaunchConfigurationsDialog.java:1516)
    at org.eclipse.debug.ui.AbstractLaunchConfigurationTab.updateLaunchConfigurationDialog(AbstractLaunchConfigurationTab.java:107)
    at org.eclipse.debug.ui.AbstractLaunchConfigurationTab$1.runInUIThread(AbstractLaunchConfigurationTab.java:430)
    at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95)
    at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
    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:1132)
    at org.eclipse.debug.ui.DebugUITools$2.run(DebugUITools.java:579)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
    at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:587)
    at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:521)
    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:1258)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
    at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    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:344)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1386)

What Eclipse version are you using ?
Latest stable
eclipse.buildId=M20120208-0800

What Run-Jetty-Run version are you using?
Latest
1.3.3.201203161919

What OS are you using ? 32bit or 64 bit?
64 bit

Please provide any additional information below.

eclipse.buildId=M20120208-0800
java.version=1.6.0_24
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=de_DE
Framework arguments:  -product org.eclipse.epp.package.java.product
Command-line arguments:  -os linux -ws gtk -arch x86_64 -product 
org.eclipse.epp.package.java.product

Original issue reported on code.google.com by san...@gmail.com on 24 May 2012 at 9:07

GoogleCodeExporter commented 8 years ago 
It happens when we try to fetch the classpaths of Web project and Jetty 
classpath.

Not sure what's going on but there might be a environemnt issue, 
I  will add some logging code for more information when this bug shows up in 
next version.

Original comment by tonylovejava on 1 Jan 2013 at 9:33

GoogleCodeExporter commented 8 years ago 
Is there a known workaround for this bug? I have not yet been able to get past 
this issue (Jetty and this plugin are currently unusable).

Original comment by joshua.p...@gmail.com on 15 Jan 2013 at 1:19

GoogleCodeExporter commented 8 years ago 
My suggestion is to try the latest nightly version and see if it's still 
reproducible.

http://code.google.com/p/run-jetty-run/wiki/Nightly

Original comment by tonylovejava on 17 Jan 2013 at 9:13

GoogleCodeExporter commented 8 years ago 
I had the same problem. The nightly version works better.
It does not cause an exception but reports that the current project does not 
exist.
This way I figured out that the project needs to be a Dynamic Web Project 
(Right click on project -> Configure -> Convert to Dynamic Web Project). Then 
it works just fine.

Original comment by notdiffi...@gmx.net on 14 Jun 2013 at 8:42

GoogleCodeExporter commented 8 years ago 
Completely removing the project and /or the plugin and / or the plugin folder 
and replacing does not fix this. What to need to do to purge all the 
run-jetty-run settings that are causing this to come back?

Original comment by jeremyjj...@gmail.com on 17 Dec 2013 at 3:38

GoogleCodeExporter commented 8 years ago 
I get this error if I close a project which has a run-jetty-run launch 
configuration which means I can't configure any other launch configurations, 
even those not using run-jetty-run. I have to delete the run-jetty-run launch 
configurations which is painful because I don't want to have to recreate them 
later. Or I have to make sure to never close a project which has a 
run-jetty-run launch configuration, which defeats the purpose of being able to 
close projects in the first place.

Original comment by dtimcumm...@gmail.com on 19 Jun 2014 at 12:54