[JBoss JIRA] (JBIDE-15833) Cannot import multiple quickstarts at once
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15833?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-15833.
---------------------------------
Fix Version/s: 4.1.1.CR1
Resolution: Done
One should never be able to select multiple examples at once. Fix is to disable multiple selection in FilteredTree : https://github.com/jbosstools/jbosstools-central/commit/76737f8f1c00b5d75....
Fixed in master and jbosstools-4.1.x
> Cannot import multiple quickstarts at once
> ------------------------------------------
>
> Key: JBIDE-15833
> URL: https://issues.jboss.org/browse/JBIDE-15833
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.1.1.Beta1
> Reporter: Peter Palaga
> Assignee: Fred Bricon
> Fix For: 4.1.1.CR1
>
>
> Steps to reproduce:
> * Go to New > Example > JBoss Tools > Project Examples > Portal Applications
> * Select two or more quickstarts, e.g. Simplest Hello World Portlet and JSF2 Hello World Portlet
> * Click Next
> Issue 1:
> * Not OK: the screen contains just empty form controls
> * Expected: The screen should probably show the requirements of the first of the selected quickstarts.
> Issue 2, after clicking Next for the second time:
> * Not OK: There is one more empty screen
> * Expected: no idea
> Issue 3, after clicking Next for the third time:
> * Not OK: There is a screen which has some meaningful entries in the Requirements list, but the Description is empty
> * Expected: There should be some description in the Description field.
> Issue 4, after clicking Next for the fourth time:
> * Not OK: the Finish button is disabled and there is no sign of a message why.
> * Expected: The Finish button should either be enabled or the form should say what is missing to enable the Button
> This is also reproducible on JBDS 7.1.0.Beta1-v20131026-0928-B470.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBDS-2555) JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip
by Mustafa Musaji (JIRA)
[ https://issues.jboss.org/browse/JBDS-2555?page=com.atlassian.jira.plugin.... ]
Mustafa Musaji commented on JBDS-2555:
--------------------------------------
[~nickboldt] I agree, it would be great if we could document these options. I think the Getting Started Guide would be a better place than the User Guide though but [~mmurray] will be able to make a better decision on this.
> JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip
> ----------------------------------------------------------------------------
>
> Key: JBDS-2555
> URL: https://issues.jboss.org/browse/JBDS-2555
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central, updatesite
> Reporter: Jiri Pallich
> Assignee: Nick Boldt
> Fix For: 7.1.0.Beta1, 7.1.0.CR1
>
>
> Offline Usage of JBoss Central (Customers without or very slow Internet access)
> On-line once, then off-line - aka a user demo/instructional class - the testLocal cache is usable/complete after one on-line install. Provide a script that pre-caches everything for an instructor/demo'er in the field (online once, then offline).
> Related to: https://issues.jboss.org/browse/JBDS-2535
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15833) Cannot import multiple quickstarts at once
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15833?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-15833:
-----------------------------------
Assignee: Fred Bricon
> Cannot import multiple quickstarts at once
> ------------------------------------------
>
> Key: JBIDE-15833
> URL: https://issues.jboss.org/browse/JBIDE-15833
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.1.1.Beta1
> Reporter: Peter Palaga
> Assignee: Fred Bricon
>
> Steps to reproduce:
> * Go to New > Example > JBoss Tools > Project Examples > Portal Applications
> * Select two or more quickstarts, e.g. Simplest Hello World Portlet and JSF2 Hello World Portlet
> * Click Next
> Issue 1:
> * Not OK: the screen contains just empty form controls
> * Expected: The screen should probably show the requirements of the first of the selected quickstarts.
> Issue 2, after clicking Next for the second time:
> * Not OK: There is one more empty screen
> * Expected: no idea
> Issue 3, after clicking Next for the third time:
> * Not OK: There is a screen which has some meaningful entries in the Requirements list, but the Description is empty
> * Expected: There should be some description in the Description field.
> Issue 4, after clicking Next for the fourth time:
> * Not OK: the Finish button is disabled and there is no sign of a message why.
> * Expected: The Finish button should either be enabled or the form should say what is missing to enable the Button
> This is also reproducible on JBDS 7.1.0.Beta1-v20131026-0928-B470.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBDS-2739) Support per-application environment variables for OpenShift
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBDS-2739?page=com.atlassian.jira.plugin.... ]
Marián Labuda closed JBDS-2739.
-------------------------------
Verified in JBDS 7.1.0.Beta1
Build id: Beta1-v20131102-1529-B493
> Support per-application environment variables for OpenShift
> -----------------------------------------------------------
>
> Key: JBDS-2739
> URL: https://issues.jboss.org/browse/JBDS-2739
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: openshift
> Reporter: Andy Goldstein
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: openshift
> Fix For: 7.1.0.Beta1
>
>
> OpenShift will soon add support for per-application environment variables. This includes:
> - specifying 1 or more environment variables at app creation
> - adding 1 or more environment variables to an app
> - deleting 1 or more environment variables from an app
> - listing an app's environment variables
> - showing the values of 1 or more environment variables for an app
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15812) Can't restart application through server adapter
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15812?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-15812.
---------------------------------
Verified in JBDS 7.1.0.Beta1
Build id: Beta1-v20131102-1529-B493
> Can't restart application through server adapter
> ------------------------------------------------
>
> Key: JBIDE-15812
> URL: https://issues.jboss.org/browse/JBIDE-15812
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Marián Labuda
> Assignee: Max Rydahl Andersen
> Labels: respin-b
> Fix For: 4.1.1.Beta1
>
>
> ASSERT: have created OpenShift application
> EXEC: restart through OpenShift explorer
> ASSERT: application is restarting
> EXEC: restart through created server adapter (context menu -> OpenShift -> Restart Aplication)
> ASSERT: nothing happens
> In the Eclipse log you'll spot the following:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.express.internal.ui.job.RestartApplicationJob.<init>(RestartApplicationJob.java:33)
> at org.jboss.tools.openshift.express.internal.ui.serverviewer.actionDelegate.RestartApplicationActionProvider$RestartApplicationAction.restartApplication(RestartApplicationActionProvider.java:48)
> at org.jboss.tools.openshift.express.internal.ui.serverviewer.actionDelegate.RestartApplicationActionProvider$RestartApplicationAction.run(RestartApplicationActionProvider.java:42)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> 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:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> 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:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15840) CLONE - Can't restart application through server adapter
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15840?page=com.atlassian.jira.plugi... ]
Marián Labuda resolved JBIDE-15840.
-----------------------------------
Resolution: Done
> CLONE - Can't restart application through server adapter
> --------------------------------------------------------
>
> Key: JBIDE-15840
> URL: https://issues.jboss.org/browse/JBIDE-15840
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Marián Labuda
> Assignee: Max Rydahl Andersen
> Fix For: 4.2.0.Alpha1
>
>
> ASSERT: have created OpenShift application
> EXEC: restart through OpenShift explorer
> ASSERT: application is restarting
> EXEC: restart through created server adapter (context menu -> OpenShift -> Restart Aplication)
> ASSERT: nothing happens
> In the Eclipse log you'll spot the following:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.express.internal.ui.job.RestartApplicationJob.<init>(RestartApplicationJob.java:33)
> at org.jboss.tools.openshift.express.internal.ui.serverviewer.actionDelegate.RestartApplicationActionProvider$RestartApplicationAction.restartApplication(RestartApplicationActionProvider.java:48)
> at org.jboss.tools.openshift.express.internal.ui.serverviewer.actionDelegate.RestartApplicationActionProvider$RestartApplicationAction.run(RestartApplicationActionProvider.java:42)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> 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:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> 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:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15812) Can't restart application through server adapter
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15812?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-15812:
----------------------------------
Fix Version/s: (was: 4.2.0.Alpha1)
> Can't restart application through server adapter
> ------------------------------------------------
>
> Key: JBIDE-15812
> URL: https://issues.jboss.org/browse/JBIDE-15812
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1
> Reporter: Marián Labuda
> Assignee: Max Rydahl Andersen
> Labels: respin-b
> Fix For: 4.1.1.Beta1
>
>
> ASSERT: have created OpenShift application
> EXEC: restart through OpenShift explorer
> ASSERT: application is restarting
> EXEC: restart through created server adapter (context menu -> OpenShift -> Restart Aplication)
> ASSERT: nothing happens
> In the Eclipse log you'll spot the following:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.express.internal.ui.job.RestartApplicationJob.<init>(RestartApplicationJob.java:33)
> at org.jboss.tools.openshift.express.internal.ui.serverviewer.actionDelegate.RestartApplicationActionProvider$RestartApplicationAction.restartApplication(RestartApplicationActionProvider.java:48)
> at org.jboss.tools.openshift.express.internal.ui.serverviewer.actionDelegate.RestartApplicationActionProvider$RestartApplicationAction.run(RestartApplicationActionProvider.java:42)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> 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:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> 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:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15840) CLONE - Can't restart application through server adapter
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15840?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-15840:
----------------------------------
Affects Version/s: (was: 4.1.1.Beta1)
> CLONE - Can't restart application through server adapter
> --------------------------------------------------------
>
> Key: JBIDE-15840
> URL: https://issues.jboss.org/browse/JBIDE-15840
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Marián Labuda
> Assignee: Max Rydahl Andersen
> Labels: respin-b
> Fix For: 4.2.0.Alpha1
>
>
> ASSERT: have created OpenShift application
> EXEC: restart through OpenShift explorer
> ASSERT: application is restarting
> EXEC: restart through created server adapter (context menu -> OpenShift -> Restart Aplication)
> ASSERT: nothing happens
> In the Eclipse log you'll spot the following:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.express.internal.ui.job.RestartApplicationJob.<init>(RestartApplicationJob.java:33)
> at org.jboss.tools.openshift.express.internal.ui.serverviewer.actionDelegate.RestartApplicationActionProvider$RestartApplicationAction.restartApplication(RestartApplicationActionProvider.java:48)
> at org.jboss.tools.openshift.express.internal.ui.serverviewer.actionDelegate.RestartApplicationActionProvider$RestartApplicationAction.run(RestartApplicationActionProvider.java:42)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> 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:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> 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:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months