You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Tim McConnell (JIRA)" <ji...@apache.org> on 2007/09/14 21:00:32 UTC
[jira] Created: (GERONIMODEVTOOLS-209) Hello World JSP does not
open in Eclipse browser when invoked with "run as, run on server" from
within Eclipse
Hello World JSP does not open in Eclipse browser when invoked with "run as, run on server" from within Eclipse
--------------------------------------------------------------------------------------------------------------
Key: GERONIMODEVTOOLS-209
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-209
Project: Geronimo-Devtools
Issue Type: Bug
Components: eclipse-plugin
Affects Versions: 2.0
Reporter: Tim McConnell
Assignee: Tim McConnell
Fix For: 2.0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-209) Hello World JSP does not
open in Eclipse browser when invoked with "run as, run on server" from
within Eclipse
Posted by "Tim McConnell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim McConnell updated GERONIMODEVTOOLS-209:
-------------------------------------------
Description:
This appears to be a WTP 2.0.x bug, not a problem with the Eclipse plugin. The Eclipse plugin is passing a valid HttpLaunchable object, with the correct url, to the WTP web client launcher class ([org.eclipse.wst.server.ui.web). But when it is ultimately ready to be launched that launchable object is null causing a NPE (stack trace below). Moving the JIRA to 2.1, and will open a bugzilla report against WTP 2.0.x.
java.lang.NullPointerException
at org.eclipse.wst.server.ui.internal.WebLaunchableClient.launch(WebLaunchableClient.java:39)
at org.eclipse.wst.server.core.internal.Client.launch(Client.java:114)
at org.eclipse.wst.server.ui.internal.LaunchClientJob$1.run(LaunchClientJob.java:79)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3659)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296)
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)
Affects Version/s: (was: 2.0)
2.1
Fix Version/s: (was: 2.0)
2.1
> Hello World JSP does not open in Eclipse browser when invoked with "run as, run on server" from within Eclipse
> --------------------------------------------------------------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-209
> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-209
> Project: Geronimo-Devtools
> Issue Type: Bug
> Components: eclipse-plugin
> Affects Versions: 2.1
> Reporter: Tim McConnell
> Assignee: Tim McConnell
> Fix For: 2.1
>
>
> This appears to be a WTP 2.0.x bug, not a problem with the Eclipse plugin. The Eclipse plugin is passing a valid HttpLaunchable object, with the correct url, to the WTP web client launcher class ([org.eclipse.wst.server.ui.web). But when it is ultimately ready to be launched that launchable object is null causing a NPE (stack trace below). Moving the JIRA to 2.1, and will open a bugzilla report against WTP 2.0.x.
> java.lang.NullPointerException
> at org.eclipse.wst.server.ui.internal.WebLaunchableClient.launch(WebLaunchableClient.java:39)
> at org.eclipse.wst.server.core.internal.Client.launch(Client.java:114)
> at org.eclipse.wst.server.ui.internal.LaunchClientJob$1.run(LaunchClientJob.java:79)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3659)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296)
> 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)
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Updated: (GERONIMODEVTOOLS-209) Hello World JSP does not
open in Eclipse browser when invoked with "run as, run on server" from within
Eclipse
Posted by Donald Woods <dw...@apache.org>.
Moved to a 2.0.x release, based on Shiva's last comment that WTP 2.0RC2 fixed
part of the problem, but plans using 2.0 schema still wouldn't work....
-Donald
Donald Woods (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Donald Woods updated GERONIMODEVTOOLS-209:
> ------------------------------------------
>
> Affects Version/s: (was: 2.1)
> 2.0
> Fix Version/s: (was: 2.1)
> 2.0.x
>
> This affects the 2.0.0 plugin and should be fixed ASAP in a 2.0.x plugin release, so we can support Geronimo 2.0 deployment plans.
> Also, please try to keep the first 2 digits of a plugin release in sync with the Geornimo Server, which we haven't done in the past and caused great user confusion....
>
>
>> Hello World JSP does not open in Eclipse browser when invoked with "run as, run on server" from within Eclipse
>> --------------------------------------------------------------------------------------------------------------
>>
>> Key: GERONIMODEVTOOLS-209
>> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-209
>> Project: Geronimo-Devtools
>> Issue Type: Bug
>> Components: eclipse-plugin
>> Affects Versions: 2.0
>> Reporter: Tim McConnell
>> Assignee: Tim McConnell
>> Fix For: 2.0.x
>>
>>
>> This appears to be a WTP 2.0.x bug, not a problem with the Eclipse plugin. The Eclipse plugin is passing a valid HttpLaunchable object, with the correct url, to the WTP web client launcher class ([org.eclipse.wst.server.ui.web). But when it is ultimately ready to be launched that launchable object is null causing a NPE (stack trace below). Moving the JIRA to 2.1, and will open a bugzilla report against WTP 2.0.x.
>> java.lang.NullPointerException
>> at org.eclipse.wst.server.ui.internal.WebLaunchableClient.launch(WebLaunchableClient.java:39)
>> at org.eclipse.wst.server.core.internal.Client.launch(Client.java:114)
>> at org.eclipse.wst.server.ui.internal.LaunchClientJob$1.run(LaunchClientJob.java:79)
>> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
>> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
>> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3659)
>> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296)
>> 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)
>>
>
[jira] Updated: (GERONIMODEVTOOLS-209) Hello World JSP does not
open in Eclipse browser when invoked with "run as, run on server" from
within Eclipse
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated GERONIMODEVTOOLS-209:
------------------------------------------
Affects Version/s: (was: 2.1)
2.0
Fix Version/s: (was: 2.1)
2.0.x
This affects the 2.0.0 plugin and should be fixed ASAP in a 2.0.x plugin release, so we can support Geronimo 2.0 deployment plans.
Also, please try to keep the first 2 digits of a plugin release in sync with the Geornimo Server, which we haven't done in the past and caused great user confusion....
> Hello World JSP does not open in Eclipse browser when invoked with "run as, run on server" from within Eclipse
> --------------------------------------------------------------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-209
> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-209
> Project: Geronimo-Devtools
> Issue Type: Bug
> Components: eclipse-plugin
> Affects Versions: 2.0
> Reporter: Tim McConnell
> Assignee: Tim McConnell
> Fix For: 2.0.x
>
>
> This appears to be a WTP 2.0.x bug, not a problem with the Eclipse plugin. The Eclipse plugin is passing a valid HttpLaunchable object, with the correct url, to the WTP web client launcher class ([org.eclipse.wst.server.ui.web). But when it is ultimately ready to be launched that launchable object is null causing a NPE (stack trace below). Moving the JIRA to 2.1, and will open a bugzilla report against WTP 2.0.x.
> java.lang.NullPointerException
> at org.eclipse.wst.server.ui.internal.WebLaunchableClient.launch(WebLaunchableClient.java:39)
> at org.eclipse.wst.server.core.internal.Client.launch(Client.java:114)
> at org.eclipse.wst.server.ui.internal.LaunchClientJob$1.run(LaunchClientJob.java:79)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3659)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296)
> 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)
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-209) Hello World JSP does not
open in Eclipse browser when invoked with "run as, run on server" from
within Eclipse
Posted by "Shiva Kumar H R (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shiva Kumar H R resolved GERONIMODEVTOOLS-209.
----------------------------------------------
Resolution: Fixed
Assignee: Shiva Kumar H R (was: Tim McConnell)
Haven't encountered this in all my tests so far with GEP trunk. Looks like WTP latest levels or some other change in GEP has fixed this. Hence closing this.
> Hello World JSP does not open in Eclipse browser when invoked with "run as, run on server" from within Eclipse
> --------------------------------------------------------------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-209
> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-209
> Project: Geronimo-Devtools
> Issue Type: Bug
> Components: eclipse-plugin
> Affects Versions: 2.0.0
> Reporter: Tim McConnell
> Assignee: Shiva Kumar H R
> Fix For: 2.1.0
>
>
> This appears to be a WTP 2.0.x bug, not a problem with the Eclipse plugin. The Eclipse plugin is passing a valid HttpLaunchable object, with the correct url, to the WTP web client launcher class ([org.eclipse.wst.server.ui.web). But when it is ultimately ready to be launched that launchable object is null causing a NPE (stack trace below). Moving the JIRA to 2.1, and will open a bugzilla report against WTP 2.0.x.
> java.lang.NullPointerException
> at org.eclipse.wst.server.ui.internal.WebLaunchableClient.launch(WebLaunchableClient.java:39)
> at org.eclipse.wst.server.core.internal.Client.launch(Client.java:114)
> at org.eclipse.wst.server.ui.internal.LaunchClientJob$1.run(LaunchClientJob.java:79)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3659)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296)
> 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)
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-209) Hello World JSP does not
open in Eclipse browser when invoked with "run as, run on server" from
within Eclipse
Posted by "Tim McConnell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim McConnell updated GERONIMODEVTOOLS-209:
-------------------------------------------
Fix Version/s: (was: 2.0.x)
2.1.0
> Hello World JSP does not open in Eclipse browser when invoked with "run as, run on server" from within Eclipse
> --------------------------------------------------------------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-209
> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-209
> Project: Geronimo-Devtools
> Issue Type: Bug
> Components: eclipse-plugin
> Affects Versions: 2.0.0
> Reporter: Tim McConnell
> Assignee: Tim McConnell
> Fix For: 2.1.0
>
>
> This appears to be a WTP 2.0.x bug, not a problem with the Eclipse plugin. The Eclipse plugin is passing a valid HttpLaunchable object, with the correct url, to the WTP web client launcher class ([org.eclipse.wst.server.ui.web). But when it is ultimately ready to be launched that launchable object is null causing a NPE (stack trace below). Moving the JIRA to 2.1, and will open a bugzilla report against WTP 2.0.x.
> java.lang.NullPointerException
> at org.eclipse.wst.server.ui.internal.WebLaunchableClient.launch(WebLaunchableClient.java:39)
> at org.eclipse.wst.server.core.internal.Client.launch(Client.java:114)
> at org.eclipse.wst.server.ui.internal.LaunchClientJob$1.run(LaunchClientJob.java:79)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3659)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296)
> 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)
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.