search

zhyh1105 / run-jetty-run

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

Can't launch jetty from Eclipse 3.4 / Ganymede #16

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Open run configuration
2. Double click on Jetty, enter in information
3. click on "Run"

What is the expected output? What do you see instead?
The archive: C:/Program
Files/eclipse/configuration/org.eclipse.osgi/bundles/393/1/.cp/lib/run-jetty-run
-bootstrap.jar
which is referenced by the classpath, does not exist.

What version of the product are you using? On what operating system?
1.0.1 of run-jetty-run in Eclipse 3.4.0 build I20080618-2000

Please provide any additional information below.
Plugin was working fine in Eclipse 3.3.

Original issue reported on code.google.com by cwil...@gmail.com on 28 Jul 2008 at 8:57

GoogleCodeExporter commented 9 years ago 
The same error happens here, also:
java.lang.NullPointerException
    at
org.eclipse.jdt.internal.launching.StandardVMDebugger.getJavaVersion(StandardVMD
ebugger.java:452)
    at
org.eclipse.jdt.internal.launching.StandardVMDebugger.run(StandardVMDebugger.jav
a:183)
    at
runjettyrun.JettyLaunchConfigurationType.launch(JettyLaunchConfigurationType.jav
a:113)
    at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.j
ava:764)
    at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.j
ava:614)
    at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:880)
    at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1083)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Original comment by gzsom...@gmail.com on 19 Aug 2008 at 1:20

GoogleCodeExporter commented 9 years ago 
I get that in 3.4 OSX :

Exception in thread "main" java.lang.NoClassDefFoundError: 
javax/servlet/http/HttpServletRequest
    at runjettyrun.Bootstrap.main(Bootstrap.java:60)

Original comment by dariusz....@gmail.com on 6 Sep 2008 at 2:55

GoogleCodeExporter commented 9 years ago 
Does anybody know what causes this error?

Original comment by jnuzhjp@gmail.com on 9 Oct 2008 at 3:17

GoogleCodeExporter commented 9 years ago 
My error is different.  When I tried to create a new run configuration, I got 
the
follow error:

An error has occurred. See error log for more details.
org.eclipse.jdt.internal.debug.ui.launcher.WorkingDirectoryBlock: method 
<init>()V
not found

Original comment by chang....@gmail.com on 9 Oct 2008 at 11:12

GoogleCodeExporter commented 9 years ago 
Anybody has any clue how to fix it for Ganymede? Showstopper here :(

Original comment by nachokb on 18 Oct 2008 at 6:37

GoogleCodeExporter commented 9 years ago 
It were a bug in Ganymede, but it's fixed in 3.4.1

Original comment by gzsom...@gmail.com on 18 Oct 2008 at 8:04

GoogleCodeExporter commented 9 years ago 
Thanks! I'll check into that.

-- nachokb

Original comment by nachokb on 18 Oct 2008 at 6:46

GoogleCodeExporter commented 9 years ago 

Hi
To fix this bug only need to add the jar "servlet-api.jar" into the classpath  
of
runjettyrun, I add the jar of tomcat

Original comment by marcg1...@gmail.com on 29 Oct 2008 at 1:58

GoogleCodeExporter commented 9 years ago 
It's should be fixed when I re-configured the jetty debug a new one , and it 
was 
still running correctly. Hopes usefully.

Original comment by harrison...@gmail.com on 5 Dec 2008 at 2:33

GoogleCodeExporter commented 9 years ago 
JettyLauncher is still broken for Eclipse 3.4.1. Fails with a "No Such Method 
Error".

To recreate: double click on "Jetty Web" under the run->run configurations menu.

Here is the log message it produces.

!ENTRY org.eclipse.jface 4 2 2009-01-26 15:16:06.924
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
!STACK 0
java.lang.NoSuchMethodError: 
org.eclipse.jdt.internal.debug.ui.launcher.WorkingDirectoryBlock: method 
<init>()V not found
    at com.iw.plugins.jetty.launcher.JettyArgumentsTab$JettyWorkingDirectoryBlock.<init>(JettyArgumentsTab.java:134)
    at com.iw.plugins.jetty.launcher.JettyArgumentsTab.createWorkingDirBlock(JettyArgumentsTab.java:107)
    at org.eclipse.jdt.debug.ui.launchConfigurations.JavaArgumentsTab.<init>(JavaArgumentsTab.java:70)
    at com.iw.plugins.jetty.launcher.JettyArgumentsTab.<init>(JettyArgumentsTab.java:57)
    at com.iw.plugins.jetty.launcher.JettyLaunchTabGroup.createTabs(JettyLaunchTabGroup.java:53)
    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupWrapper.createTabs(LaunchConfigurationTabGroupWrapper.java:62)
    at org.eclipse.debug.internal.ui.launchConfigurations.CreateLaunchConfigurationAction.performAction(CreateLaunchConfigurationAction.java:72)
    at org.eclipse.debug.internal.ui.launchConfigurations.AbstractLaunchConfigurationAction$1.run(AbstractLaunchConfigurationAction.java:103)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
    at org.eclipse.debug.internal.ui.launchConfigurations.AbstractLaunchConfigurationAction.run(AbstractLaunchConfigurationAction.java:106)
    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$2.run(LaunchConfigurationsDialog.java:537)
    at org.eclipse.debug.ui.AbstractDebugView.doubleClick(AbstractDebugView.java:729)
    at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:799)
    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:175)
    at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:797)
    at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1419)
    at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1173)
    at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:237)
    at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:234)
    at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:295)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
    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:1113)
    at org.eclipse.debug.ui.DebugUITools$1.run(DebugUITools.java:388)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
    at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:396)
    at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:332)
    at org.eclipse.debug.ui.actions.OpenLaunchDialogAction.run(OpenLaunchDialogAction.java:81)
    at org.eclipse.debug.ui.actions.OpenLaunchDialogAction.runWithEvent(OpenLaunchDialogAction.java:89)
    at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:241)
    at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)
    at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583)
    at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500)
    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:1003)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.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(EclipseStarter.java:386)
    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:585)
    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)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1212)

Original comment by RobB...@gmail.com on 26 Jan 2009 at 9:20

GoogleCodeExporter commented 9 years ago 
any ETA when is will be fixed :(

Original comment by milky...@gmail.com on 17 Feb 2009 at 6:26

GoogleCodeExporter commented 9 years ago 
Please try version 1.1 to see if it addresses the problem (it changes the way 
the 
class path is handled).

Thanks, James

Original comment by James.Sy...@gmail.com on 4 May 2009 at 12:36

GoogleCodeExporter commented 9 years ago

Original comment by James.Sy...@gmail.com on 4 May 2009 at 12:36

GoogleCodeExporter commented 9 years ago 
My error is different.  When I tried to create a new run configuration, I got 
the
follow error:

An error has occurred. See error log for more details.
org.eclipse.jdt.internal.debug.ui.launcher.WorkingDirectoryBlock: method 
<init>()V
not found

me too

how to solve this problem

Original comment by zxchhu...@gmail.com on 5 May 2009 at 9:44

GoogleCodeExporter commented 9 years ago 
Judging from the stack trace in
comment 10 (http://code.google.com/p/run-jetty-run/issues/detail?id=16#c10)
that is unrelated to this plugin:

java.lang.NoSuchMethodError: 
org.eclipse.jdt.internal.debug.ui.launcher.WorkingDirectoryBlock: method 
<init>()V not found
    at com.iw.plugins.jetty.launcher.JettyArgumentsTab$JettyWorkingDirectoryBlock.<init>(JettyArgumentsTab.java:134)
    at com.iw.plugins.jetty.launcher.JettyArgumentsTab.createWorkingDirBlock(JettyArgumentsTab.java:107)
    at org.eclipse.jdt.debug.ui.launchConfigurations.JavaArgumentsTab.<init>(JavaArgumentsTab.java:70)
    at com.iw.plugins.jetty.launcher.JettyArgumentsTab.<init>(JettyArgumentsTab.java:57)
    at com.iw.plugins.jetty.launcher.JettyLaunchTabGroup.createTabs(JettyLaunchTabGroup.java:53)

RobBugh must be using some other jetty launcher.

Original comment by James.Sy...@gmail.com on 5 May 2009 at 12:13

GoogleCodeExporter commented 9 years ago 
I've tested rjr version 1.1 with eclipse 3.4, build I20080617-2000, and don't 
see a 
stack trace as reported.

Original comment by James.Sy...@gmail.com on 5 May 2009 at 12:14

GoogleCodeExporter commented 9 years ago 
I also see this issue after installing run-jetty 1.1.1 on eclipse 3.4.2 on 
linux. I
don't know anything about osgi, but the problem seems to be with the install 
process,
which fails to extract jars required for the jetty runtime.

To fix, I noted the path mentioned in the error message:

    "The archive:
/usr/local/eclipse/configuration/org.eclipse.osgi/bundles/393/1/.cp/lib/run-jett
y-run-bootstrap.jar
which is referenced by the classpath, does not exist."

Then I created the non-existent path being referenced, and extracted the 
required
jars from the run-jetty plugin:

mkdir -p /usr/local/eclipse/configuration/org.eclipse.osgi/bundles/393/1/.cp
cd /usr/local/eclipse/configuration/org.eclipse.osgi/bundles/393/1/.cp
jar xvf /usr/local/eclipse/plugins/runjettyrun_1.1.1.jar lib

Voila. 
Now run-jetty is happy again.

Original comment by hodges.d...@gmail.com on 19 May 2009 at 11:19

GoogleCodeExporter commented 9 years ago 
Did you get any errors during the install?  Did it work at any time?

Original comment by James.Sy...@gmail.com on 21 May 2009 at 12:20

GoogleCodeExporter commented 9 years ago 
I saw no problems when installing, nor when creating the run-jetty Run
Configuration(s). But executing any run-jetty Run Configuration would always 
produce
the error message above.

Original comment by hodges.d...@gmail.com on 21 May 2009 at 12:46

GoogleCodeExporter commented 9 years ago 
It looks like this bug is still here, in Eclipse Galileo 3.5.1 (quite fresh, 
not-APT
install on Linux Mint 7 Gloria):

java.lang.NoClassDefFoundError:
org/eclipse/jdt/internal/debug/ui/launcher/WorkingDirectoryBlock
at
com.iw.plugins.jetty.launcher.JettyLaunchTabGroup.createTabs(JettyLaunchTabGroup
.java:53)
at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupWr
apper.createTabs(LaunchConfigurationTabGroupWrapper.java:137)
at
org.eclipse.debug.internal.ui.launchConfigurations.CreateLaunchConfigurationActi
on.performAction(CreateLaunchConfigurationAction.java:72)
at
org.eclipse.debug.internal.ui.launchConfigurations.AbstractLaunchConfigurationAc
tion$1.run(AbstractLaunchConfigurationAction.java:103)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at
org.eclipse.debug.internal.ui.launchConfigurations.AbstractLaunchConfigurationAc
tion.run(AbstractLaunchConfigurationAction.java:106)
at
org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionLis
tenerAction.java:168)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionCont
ributionItem.java:584)
at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.
java:501)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContribution
Item.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112)
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.op
en(LaunchConfigurationsDialog.java:1064)
at org.eclipse.debug.ui.DebugUITools$1.run(DebugUITools.java:398)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at
org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITo
ols.java:406)
at
org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITo
ols.java:340)
at
org.eclipse.debug.ui.actions.OpenLaunchDialogAction.run(OpenLaunchDialogAction.j
ava:81)
at
org.eclipse.debug.ui.actions.OpenLaunchDialogAction.runWithEvent(OpenLaunchDialo
gAction.java:89)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:241)
at 
org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionCont
ributionItem.java:584)
at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.
java:501)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContribution
Item.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at 
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java
:113)
at 
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Ecli
pseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLau
ncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
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:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
Caused by: java.lang.ClassNotFoundException:
org.eclipse.jdt.internal.debug.ui.launcher.WorkingDirectoryBlock
at 
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.jav
a:494)
at 
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)
at 
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:398)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassL
oader.java:105)
at java.lang.ClassLoader.loadClass(ClassLoader.java:268)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:336)
... 52 more

CU

Original comment by alexbott...@gmail.com on 9 Nov 2009 at 10:51

GoogleCodeExporter commented 9 years ago 
i use eclipse Helios Release.when i double click the jetty run .
it was show the error:
An error has occurred. See error log for more details.
org/eclipse/jdt/internal/debug/ui/launcher/WorkingDirectoryBlock
can anybody slove it?

Original comment by vsko...@gmail.com on 22 Jul 2010 at 12:13

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Check your run configuration first and see if there's any error.

Original comment by tonylovejava on 16 Mar 2011 at 4:59

GoogleCodeExporter commented 9 years ago 
All people getting this error:

An error has occurred. See error log for more details.
org/eclipse/jdt/internal/debug/ui/launcher/WorkingDirectoryBlock

Your are using the JettyLauncher (updated for Jetty 6) on Eclipse Helios. 
JettyLauncher was discontinued.

This page is about "Run Jetty Run" project, so, use it instead of JettyLauncher.

Original comment by rael...@gmail.com on 16 Mar 2011 at 11:04

GoogleCodeExporter commented 9 years ago 
Dear all ,if you got similar problem with this one , 
please OPEN A NEW ISSUE and provide more detail ,or it's hard to trace it.

Original comment by tonylovejava on 16 Mar 2011 at 9:06

GoogleCodeExporter commented 9 years ago 
com.google.gdt.eclipse.platform.e36_1.4.0.v201010280102.jar

this jar can reslove these problem ... I had done it

Original comment by fzhu...@gmail.com on 1 Apr 2011 at 9:04

GoogleCodeExporter commented 9 years ago 
Hello,

impossible for me to install plugin rjr with the update url provided on the 
official site.
wat do ?

Original comment by ybor...@gmail.com on 19 May 2011 at 1:18

GoogleCodeExporter commented 9 years ago 
Hi ybor , 

I am not sure for the "impossible" you mean ,
do you meet any issue or any error while you are trying to access update site?

And which Eclipse version you are using ? Also Eclipse 3.4?

Please feel free to post a new issue for it and give us more information , 
If I could reproduce it , I will test it and get a new release to handle that.

Thanks for your understanding.
Tony

Original comment by tonylovejava on 19 May 2011 at 4:12