[JBoss JIRA] (JBTIS-25) SwitchYard 0.5.0 requires Guvnor 5.4, but 5.3 is on the 3.3.x nightly site
by Rob Cernich (JIRA)
[ https://issues.jboss.org/browse/JBTIS-25?page=com.atlassian.jira.plugin.s... ]
Rob Cernich resolved JBTIS-25.
------------------------------
Resolution: Out of Date
> SwitchYard 0.5.0 requires Guvnor 5.4, but 5.3 is on the 3.3.x nightly site
> --------------------------------------------------------------------------
>
> Key: JBTIS-25
> URL: https://issues.jboss.org/browse/JBTIS-25
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: switchyard
> Reporter: Nick Boldt
> Assignee: Rob Cernich
> Fix For: 4.0.0
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> (2012-05-31 11:49:50) nboldt: rcernich: can you install your stuff into a clean eclipse instance from here? http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/3.3.x.Ni...
> (2012-05-31 11:50:19) nboldt: rcernich: contains SY 0.5.0.v20120530-0222-H91-CI
> (2012-05-31 11:50:41) nboldt: should be able to resolve ALL your upstream needs, from eclipse.org, m2e, jboss.org, etc.
> (2012-05-31 11:50:12) rcernich: nboldt: pretty sure
> (2012-05-31 11:50:42) rcernich: nboldt: dependencies are mostly limited to m2e, emf, wtp
> (2012-05-31 11:50:57) rcernich: nboldt: jboss m2e is optional
> (2012-05-31 11:51:16) rcernich: nboldt: we have some features waiting in the wings for guvnor integration
> (2012-05-31 11:51:26) rcernich: nboldt: but that requires guvnor 5.4 tools
> (2012-05-31 12:33:50) nboldt: rcernich: looks like we're pulling 5.3.2 into SOA Tooling https://hudson.qa.jboss.com/hudson/view/SOA-Team/view/SOATools-3.3.0/job/...
> (2012-05-31 12:35:16) nboldt: if you need 5.4 droolsjbpm stuff in soa tooling site so it's available when installing switchyard 0.5.0, then ... this is a problem and you need to get Doug on it.
> (2012-05-31 12:36:15) nboldt: https://repository.jboss.org/nexus/content/groups/public/org/drools/org.d... is out
> If I understand the issue, you want to include SY 0.5.0 in SOATools 3.3.0.Beta3, but that requires Guvnor 5.4.0.Final, which is not as yet being aggregated.
> Integrate http://download.jboss.org/drools/release/5.4.0.Final/org.drools.updatesite/ into the staging composite site [1] for SOA Tooling 3.3.x.Nightly instead of the 5.3.2 bits.
> [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooli...
--
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
11 years
[JBoss JIRA] (JBDS-2374) Cannot install JBoss SwitchYard tools into JBDS 6.0
by Rob Cernich (JIRA)
[ https://issues.jboss.org/browse/JBDS-2374?page=com.atlassian.jira.plugin.... ]
Rob Cernich reassigned JBDS-2374:
---------------------------------
Assignee: Len DiMaggio (was: Rob Cernich)
Hey Len,
Can you close or reassign this?
Thanks,
Rob
> Cannot install JBoss SwitchYard tools into JBDS 6.0
> ---------------------------------------------------
>
> Key: JBDS-2374
> URL: https://issues.jboss.org/browse/JBDS-2374
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: SOA Tooling / Platform
> Affects Versions: 6.0.0.Alpha1-SOA
> Environment: Version: 6.0.0.Beta1
> Build id: Beta1-v20121024-2033-B58
> Build date: 20121024-2033
> Reporter: Len DiMaggio
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 6.0.0.Alpha1-SOA
>
>
> It's possible to successfully install SwitchYard eclipse tools into Eclipse Juno, if these update sites are defined to resolve dependencies:
> JBT - http://download.jboss.org/jbosstools/updates/development/juno/
> m2e - http://download.jboss.org/jbosstools/updates/m2eclipse-wtp/
> SY - jar:file:/jboss/local/downloads/switchyard-site-assembly-0.6.0.Beta2.zip!/
> EMF - http://download.eclipse.org/modeling/emf/updates/releases/
> GEF - http://download.eclipse.org/tools/gef/updates/releases/
> But - trying to install SwitchYard eclipse tools into JBDS 6.0.beta1 fails with this dependency error:
> Cannot complete the install because one or more required items could not be found.
> Software being installed: SwitchYard Tools 0.6.0.v20121031-1758-H213-Beta2 (org.switchyard.tools.feature.feature.group 0.6.0.v20121031-1758-H213-Beta2)
> Missing requirement: SwitchYard Tools 0.6.0.v20121031-1758-H213-Beta2 (org.switchyard.tools.feature.feature.group 0.6.0.v20121031-1758-H213-Beta2) requires 'org.maven.ide.eclipse.wtp.feature.feature.group 0.14.0' but it could not be found
> Adding this update site:
> http://download.jboss.org/jbosstools/updates/m2eclipse-wtp/
> Results in this error:
> Cannot complete the install because of a conflicting dependency.
> Software being installed: SwitchYard Tools 0.6.0.v20121031-1758-H213-Beta2 (org.switchyard.tools.feature.feature.group 0.6.0.v20121031-1758-H213-Beta2)
> Software currently installed: JBoss Developer Studio (Branded Product) 6.0.0.Beta1-v20121024-2033-B58 (com.jboss.jbds.all 6.0.0.Beta1-v20121024-2033-B58)
> Only one of the following can be installed at once:
> Maven Integration for Eclipse WTP 0.15.3.20120830-0850 (org.maven.ide.eclipse.wtp 0.15.3.20120830-0850)
> This version of m2e-wtp cannot be installed on top of the already installed m2eclipse-wtp. Uninstall the previous version of m2eclipse-wtp and try the install again. 0.16.0.20120914-0945 (org.maven.ide.eclipse.wtp 0.16.0.20120914-0945)
--
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
11 years
[JBoss JIRA] (JBTIS-70) JBTIS Kepler component content
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-70?page=com.atlassian.jira.plugin.s... ]
Paul Leacu commented on JBTIS-70:
---------------------------------
Hey Rob -
Yes - I reworded it so that the component owner should specify a compatible component - not necessarily rebuild it.
Thanks,
--paull
> JBTIS Kepler component content
> ------------------------------
>
> Key: JBTIS-70
> URL: https://issues.jboss.org/browse/JBTIS-70
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: BPEL, BPMN2, drools/ jBPM5, ESB, Fuse IDE, modeshape, savara, switchyard, teiid
> Affects Versions: 4.1.0
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.1.0
>
>
> Welcome to Kepler.
> JBTIS 4.1.0/JBDSIS 7.0.0 is now available on master/trunk. This is needed for JBDS 7.0 in SOA-P 6.0 Beta. Please specify your compatible component for Kepler and update your contribution to the integration stack. The release procedure is here:
> https://community.jboss.org/wiki/IntegrationToolingReleaseProcess
> The specific files to change are:
> https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jb...
> https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jb...
> https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de...
> https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de...
> The Kepler JBTIS target platform is here:
> https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
> I'll process the PR and regenerate the aggregate update site.
> Thanks!
> --paull
--
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
11 years
[JBoss JIRA] (JBIDE-14358) Not able to generate JBOSS WS client code in eclispe Juno
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14358?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick updated JBIDE-14358:
--------------------------------------
Assignee: Brian Fitzpatrick
> Not able to generate JBOSS WS client code in eclispe Juno
> ---------------------------------------------------------
>
> Key: JBIDE-14358
> URL: https://issues.jboss.org/browse/JBIDE-14358
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Environment: EAP 5.1.0
> Reporter: Roopa Chakra
> Assignee: Brian Fitzpatrick
>
> Tried installing JBoss tools (JBoss Tools (Juno) 4.0.1.Final from eclipse market place) to eclipse juno. Set the JBOSS WS run time location by following steps.
>
> Window->Preferences->Web Services->JBossWS Preferences->Add. Then provide a name (eg. jboss-eap-5.1.0), Home Folder should be $JBOSS_HOME (which is the jboss-as folder). JBOSS server is EAP 5.1.0.
> When I right click on existing wsdl to generate client code I get below exception.
> Not sure why tools is not able to find JBOSSWS runtime location.
>
> IWAB0014E Unexpected exception occurred.
>
> java.lang.NullPointerException
> at org.jboss.tools.ws.creation.core.utils.JBossWSCreationUtils.getJBossWSRuntimeLocation(JBossWSCreationUtils.java:296)
> at org.jboss.tools.ws.creation.core.commands.InitialClientCommand.execute(InitialClientCommand.java:62)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:254)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1028)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:264)
> at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:91)
> at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:154)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:136)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:908)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
> at org.eclipse.jface.window.Window.open(Window.java:801)
> at org.eclipse.wst.command.internal.env.ui.widgets.popup.DynamicPopupWizard.run(DynamicPopupWizard.java:130)
> at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
> 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:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1053)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:942)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 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:353)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> 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:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)"
--
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
11 years
[JBoss JIRA] (JBIDE-14358) Not able to generate JBOSS WS client code in eclispe Juno
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14358?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick updated JBIDE-14358:
--------------------------------------
Affects Version/s: 4.0.0.Final
> Not able to generate JBOSS WS client code in eclispe Juno
> ---------------------------------------------------------
>
> Key: JBIDE-14358
> URL: https://issues.jboss.org/browse/JBIDE-14358
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 4.0.0.Final
> Environment: EAP 5.1.0
> Reporter: Roopa Chakra
> Assignee: Brian Fitzpatrick
>
> Tried installing JBoss tools (JBoss Tools (Juno) 4.0.1.Final from eclipse market place) to eclipse juno. Set the JBOSS WS run time location by following steps.
>
> Window->Preferences->Web Services->JBossWS Preferences->Add. Then provide a name (eg. jboss-eap-5.1.0), Home Folder should be $JBOSS_HOME (which is the jboss-as folder). JBOSS server is EAP 5.1.0.
> When I right click on existing wsdl to generate client code I get below exception.
> Not sure why tools is not able to find JBOSSWS runtime location.
>
> IWAB0014E Unexpected exception occurred.
>
> java.lang.NullPointerException
> at org.jboss.tools.ws.creation.core.utils.JBossWSCreationUtils.getJBossWSRuntimeLocation(JBossWSCreationUtils.java:296)
> at org.jboss.tools.ws.creation.core.commands.InitialClientCommand.execute(InitialClientCommand.java:62)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:254)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1028)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:264)
> at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:91)
> at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:154)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:136)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:908)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
> at org.eclipse.jface.window.Window.open(Window.java:801)
> at org.eclipse.wst.command.internal.env.ui.widgets.popup.DynamicPopupWizard.run(DynamicPopupWizard.java:130)
> at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
> 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:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1053)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:942)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 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:353)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> 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:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)"
--
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
11 years
[JBoss JIRA] (JBIDE-14358) Not able to generate JBOSS WS client code in eclispe Juno
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14358?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick updated JBIDE-14358:
--------------------------------------
Fix Version/s: 4.1.0.Beta1
> Not able to generate JBOSS WS client code in eclispe Juno
> ---------------------------------------------------------
>
> Key: JBIDE-14358
> URL: https://issues.jboss.org/browse/JBIDE-14358
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 4.0.0.Final
> Environment: EAP 5.1.0
> Reporter: Roopa Chakra
> Assignee: Brian Fitzpatrick
> Fix For: 4.1.0.Beta1
>
>
> Tried installing JBoss tools (JBoss Tools (Juno) 4.0.1.Final from eclipse market place) to eclipse juno. Set the JBOSS WS run time location by following steps.
>
> Window->Preferences->Web Services->JBossWS Preferences->Add. Then provide a name (eg. jboss-eap-5.1.0), Home Folder should be $JBOSS_HOME (which is the jboss-as folder). JBOSS server is EAP 5.1.0.
> When I right click on existing wsdl to generate client code I get below exception.
> Not sure why tools is not able to find JBOSSWS runtime location.
>
> IWAB0014E Unexpected exception occurred.
>
> java.lang.NullPointerException
> at org.jboss.tools.ws.creation.core.utils.JBossWSCreationUtils.getJBossWSRuntimeLocation(JBossWSCreationUtils.java:296)
> at org.jboss.tools.ws.creation.core.commands.InitialClientCommand.execute(InitialClientCommand.java:62)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:254)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1028)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:264)
> at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:91)
> at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:154)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:136)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:908)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
> at org.eclipse.jface.window.Window.open(Window.java:801)
> at org.eclipse.wst.command.internal.env.ui.widgets.popup.DynamicPopupWizard.run(DynamicPopupWizard.java:130)
> at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
> 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:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1053)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:942)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 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:353)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> 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:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)"
--
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
11 years