[JBoss JIRA] (JBIDE-21046) Need to implement "Bower Install" launch shortcut
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21046?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-21046:
--------------------------------
Description:
[Bower Install|http://bower.io/docs/api/#install] - Installs the project dependencies
>From the user perspective it will be a launch shortcut just like existing "Bower Update"
Steps to verify:
- create JavaScript project
- create *bower.json* in it via *"Bower Init"* wizard;
- add some *dependencies / devDependencies* to it (e.g. grunt / angular / jquery etc.)
- *"Bower Install"* must be available via right-clicking ( bower.json / parent folder / project / editor with opened bower.json ) -> Run As -> Bower install
- After launch all *dependencies / devDependencies* must be available in bower_component folder
was:
[Bower Install|http://bower.io/docs/api/#install] - Installs the project dependencies
>From the user perspective it will be a launch shortcut just like existing "Bower Update"
> Need to implement "Bower Install" launch shortcut
> -------------------------------------------------
>
> Key: JBIDE-21046
> URL: https://issues.jboss.org/browse/JBIDE-21046
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: nodejs
> Affects Versions: 4.3.0.Final
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Labels: new_and_noteworthy
> Fix For: 4.4.0.Alpha1
>
>
> [Bower Install|http://bower.io/docs/api/#install] - Installs the project dependencies
> From the user perspective it will be a launch shortcut just like existing "Bower Update"
> Steps to verify:
> - create JavaScript project
> - create *bower.json* in it via *"Bower Init"* wizard;
> - add some *dependencies / devDependencies* to it (e.g. grunt / angular / jquery etc.)
> - *"Bower Install"* must be available via right-clicking ( bower.json / parent folder / project / editor with opened bower.json ) -> Run As -> Bower install
> - After launch all *dependencies / devDependencies* must be available in bower_component folder
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21038) Software/Update page is not working on Fedora 23 (Beta)
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21038?page=com.atlassian.jira.plugi... ]
Radim Hopp commented on JBIDE-21038:
------------------------------------
I guess, that now I have final too... It should be done by automatic updates automatically.
[~mmalina] will install new Fedora 23 slave to our lab in a matter of days and then I'll try it on another machine.
If you want feedback sooner than in a few days, I can try to persuade somebody with F23 outside of our team to try it for me ;-)
> Software/Update page is not working on Fedora 23 (Beta)
> -------------------------------------------------------
>
> Key: JBIDE-21038
> URL: https://issues.jboss.org/browse/JBIDE-21038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Final
> Environment: JBDS 9.0.0.GA
> Reporter: Radim Hopp
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Recently I upgraded my system to Fedora 23 (beta) and second page of Cetnral (Software/Update) is not working. It is rendered with "Refreshing..." text and carousel (which is not spinning as it should). One processor core goes 100%.
> java version "1.8.0_65"
> gtk3 version 3.18.2
> jstack: http://pastebin.com/a7U02yjt
> Everything is fine with GTK2.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBTIS-531) Bouncy Castle causes Fuse Tooling full source TP build failure.
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/JBTIS-531?page=com.atlassian.jira.plugin.... ]
Paul Richardson edited comment on JBTIS-531 at 11/5/15 4:25 AM:
----------------------------------------------------------------
[~mickael_istria]
-Can you please address my question [here|https://github.com/jbosstools/jbosstools-locus/pull/50#issuecomment-...
Never mind, you're way ahead of me!
Many thanks
was (Author: phantomjinx):
[~mickael_istria]
Can you please address my question [here|https://github.com/jbosstools/jbosstools-locus/pull/50#issuecomment-...].
Many thanks
> Bouncy Castle causes Fuse Tooling full source TP build failure.
> ---------------------------------------------------------------
>
> Key: JBTIS-531
> URL: https://issues.jboss.org/browse/JBTIS-531
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 9.0.0.Alpha2, 8.0.4.CR2
> Reporter: Paul Leacu
> Assignee: Paul Richardson
> Priority: Blocker
>
> Here is the issue. The JBTIS TP has a reliance on bouncycastle that was introduced as an indirect dependency by Teiid Designer because they needed the Apache directory features including the org.apache.directory.studio.connection.ui feature. The bcprov feature was removed from the JBTIS TP and Teiid Designer added a dummy feature to satisfy maven. This was built and everything in the IS builds and installs fine - no one directly needed bouncycastle.
> Fuse Tooling builds a local development-only full source target platform based on the JBTIS TP. This causes all dependencies to be fully resolved which causes them to fail their target platform development-only build:
> {code}
> mvn -Pmultiple2repo -U -Dmirror-target-to-repo.includeSources=true clean install
> ...
> [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618
> [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.x509.extension 0.0.0' but it could not be found
> {code}
> you may also see this error:
> {code}
> [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618
> [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.asn1 0.0.0' but it could not be found
> {code}
> Both of these plugins can be found (in stub form) here:
> http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac...
> How should this be fixed? Both Teiid Designer and Fuse Tooling use the JBTIS TP. Fuse needs this development TP to debug Fuse and SAP issues. They shouldn't have to incur a dependency that has nothing to do with them. If we pull the entire Apache directory dependency block out of the IS TP then Teiid Des will have to go back to creating their own merged TP.
> WDYT?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBTIS-531) Bouncy Castle causes Fuse Tooling full source TP build failure.
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/JBTIS-531?page=com.atlassian.jira.plugin.... ]
Paul Richardson commented on JBTIS-531:
---------------------------------------
[~mickael_istria]
Can you please address my question [here|https://github.com/jbosstools/jbosstools-locus/pull/50#issuecomment-...].
Many thanks
> Bouncy Castle causes Fuse Tooling full source TP build failure.
> ---------------------------------------------------------------
>
> Key: JBTIS-531
> URL: https://issues.jboss.org/browse/JBTIS-531
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 9.0.0.Alpha2, 8.0.4.CR2
> Reporter: Paul Leacu
> Assignee: Paul Richardson
> Priority: Blocker
>
> Here is the issue. The JBTIS TP has a reliance on bouncycastle that was introduced as an indirect dependency by Teiid Designer because they needed the Apache directory features including the org.apache.directory.studio.connection.ui feature. The bcprov feature was removed from the JBTIS TP and Teiid Designer added a dummy feature to satisfy maven. This was built and everything in the IS builds and installs fine - no one directly needed bouncycastle.
> Fuse Tooling builds a local development-only full source target platform based on the JBTIS TP. This causes all dependencies to be fully resolved which causes them to fail their target platform development-only build:
> {code}
> mvn -Pmultiple2repo -U -Dmirror-target-to-repo.includeSources=true clean install
> ...
> [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618
> [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.x509.extension 0.0.0' but it could not be found
> {code}
> you may also see this error:
> {code}
> [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618
> [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.asn1 0.0.0' but it could not be found
> {code}
> Both of these plugins can be found (in stub form) here:
> http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac...
> How should this be fixed? Both Teiid Designer and Fuse Tooling use the JBTIS TP. Fuse needs this development TP to debug Fuse and SAP issues. They shouldn't have to incur a dependency that has nothing to do with them. If we pull the entire Apache directory dependency block out of the IS TP then Teiid Des will have to go back to creating their own merged TP.
> WDYT?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBTIS-531) Bouncy Castle causes Fuse Tooling full source TP build failure.
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBTIS-531?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBTIS-531:
--------------------------------------
Orbit has a org.bouncycastle.bcprov bundle that contains the necessary package.
There is no need to put that in Locus, just consume the bundle from our Orbit mirror in your TP.
> Bouncy Castle causes Fuse Tooling full source TP build failure.
> ---------------------------------------------------------------
>
> Key: JBTIS-531
> URL: https://issues.jboss.org/browse/JBTIS-531
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 9.0.0.Alpha2, 8.0.4.CR2
> Reporter: Paul Leacu
> Assignee: Paul Richardson
> Priority: Blocker
>
> Here is the issue. The JBTIS TP has a reliance on bouncycastle that was introduced as an indirect dependency by Teiid Designer because they needed the Apache directory features including the org.apache.directory.studio.connection.ui feature. The bcprov feature was removed from the JBTIS TP and Teiid Designer added a dummy feature to satisfy maven. This was built and everything in the IS builds and installs fine - no one directly needed bouncycastle.
> Fuse Tooling builds a local development-only full source target platform based on the JBTIS TP. This causes all dependencies to be fully resolved which causes them to fail their target platform development-only build:
> {code}
> mvn -Pmultiple2repo -U -Dmirror-target-to-repo.includeSources=true clean install
> ...
> [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618
> [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.x509.extension 0.0.0' but it could not be found
> {code}
> you may also see this error:
> {code}
> [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618
> [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.asn1 0.0.0' but it could not be found
> {code}
> Both of these plugins can be found (in stub form) here:
> http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac...
> How should this be fixed? Both Teiid Designer and Fuse Tooling use the JBTIS TP. Fuse needs this development TP to debug Fuse and SAP issues. They shouldn't have to incur a dependency that has nothing to do with them. If we pull the entire Apache directory dependency block out of the IS TP then Teiid Des will have to go back to creating their own merged TP.
> WDYT?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21038) Software/Update page is not working on Fedora 23 (Beta)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21038?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21038:
----------------------------------------
[~rhopp] can you try it on Fedora 23 Final too?
> Software/Update page is not working on Fedora 23 (Beta)
> -------------------------------------------------------
>
> Key: JBIDE-21038
> URL: https://issues.jboss.org/browse/JBIDE-21038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Final
> Environment: JBDS 9.0.0.GA
> Reporter: Radim Hopp
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Recently I upgraded my system to Fedora 23 (beta) and second page of Cetnral (Software/Update) is not working. It is rendered with "Refreshing..." text and carousel (which is not spinning as it should). One processor core goes 100%.
> java version "1.8.0_65"
> gtk3 version 3.18.2
> jstack: http://pastebin.com/a7U02yjt
> Everything is fine with GTK2.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21053) IndexOutOfBoundsException in scaffold generate wizard
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21053?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21053:
-----------------------------------
Fix Version/s: 4.3.x
4.4.x
> IndexOutOfBoundsException in scaffold generate wizard
> -----------------------------------------------------
>
> Key: JBIDE-21053
> URL: https://issues.jboss.org/browse/JBIDE-21053
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.3.0.Final
> Reporter: Pavol Srna
> Assignee: Koen Aers
> Fix For: 4.3.x, 4.4.0.Alpha1
>
>
> Message: Unhandled event loop exception during blocked modal context.
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IndexOutOfBoundsException: Index: 2, Size: 0)
> at org.eclipse.swt.SWT.error(SWT.java:4491)
> at org.eclipse.swt.SWT.error(SWT.java:4406)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:172)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:387)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002)
> at org.jboss.tools.forge.ui.internal.ext.dialog.ForgeCommandDialog.run(ForgeCommandDialog.java:56)
> at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizard.performFinish(ForgeWizard.java:97)
> at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizard.performFinish(ForgeWizard.java:87)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> 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.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:210)
> at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:102)
> at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog$1$1.handleElementSelected(UICommandListDialog.java:233)
> at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.handleSelection(QuickAccessContents.java:322)
> at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.access$0(QuickAccessContents.java:312)
> at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents$6.mouseUp(QuickAccessContents.java:461)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> Caused by: java.lang.IndexOutOfBoundsException: Index: 2, Size: 0
> at java.util.ArrayList.rangeCheck(ArrayList.java:653)
> at java.util.ArrayList.get(ArrayList.java:429)
> at org.jboss.forge.addon.ui.impl.controller.WizardCommandControllerImpl.getCurrentEntry(WizardCommandControllerImpl.java:486)
> at org.jboss.forge.addon.ui.impl.controller.WizardCommandControllerImpl.getCurrentController(WizardCommandControllerImpl.java:497)
> at org.jboss.forge.addon.ui.impl.controller.WizardCommandControllerImpl.validate(WizardCommandControllerImpl.java:214)
> at org.jboss.forge.addon.ui.impl.controller.NoUIWizardControllerDecorator.validate(NoUIWizardControllerDecorator.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
> at org.jboss.forge.addon.ui.controller.CommandController_$$_javassist_c9e95bc0-f945-4ada-ae34-ecb5817baed3.validate(CommandController_$$_javassist_c9e95bc0-f945-4ada-ae34-ecb5817baed3.java)
> at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardPage.validatePage(ForgeWizardPage.java:238)
> at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardPage.access$5(ForgeWizardPage.java:233)
> at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardPage$1$1.run(ForgeWizardPage.java:180)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 58 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21053) IndexOutOfBoundsException in scaffold generate wizard
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21053?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21053:
-----------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.4.x)
> IndexOutOfBoundsException in scaffold generate wizard
> -----------------------------------------------------
>
> Key: JBIDE-21053
> URL: https://issues.jboss.org/browse/JBIDE-21053
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.3.0.Final
> Reporter: Pavol Srna
> Assignee: Koen Aers
> Fix For: 4.3.x, 4.4.0.Alpha1
>
>
> Message: Unhandled event loop exception during blocked modal context.
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IndexOutOfBoundsException: Index: 2, Size: 0)
> at org.eclipse.swt.SWT.error(SWT.java:4491)
> at org.eclipse.swt.SWT.error(SWT.java:4406)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:172)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:387)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002)
> at org.jboss.tools.forge.ui.internal.ext.dialog.ForgeCommandDialog.run(ForgeCommandDialog.java:56)
> at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizard.performFinish(ForgeWizard.java:97)
> at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizard.performFinish(ForgeWizard.java:87)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> 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.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:210)
> at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:102)
> at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog$1$1.handleElementSelected(UICommandListDialog.java:233)
> at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.handleSelection(QuickAccessContents.java:322)
> at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.access$0(QuickAccessContents.java:312)
> at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents$6.mouseUp(QuickAccessContents.java:461)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> Caused by: java.lang.IndexOutOfBoundsException: Index: 2, Size: 0
> at java.util.ArrayList.rangeCheck(ArrayList.java:653)
> at java.util.ArrayList.get(ArrayList.java:429)
> at org.jboss.forge.addon.ui.impl.controller.WizardCommandControllerImpl.getCurrentEntry(WizardCommandControllerImpl.java:486)
> at org.jboss.forge.addon.ui.impl.controller.WizardCommandControllerImpl.getCurrentController(WizardCommandControllerImpl.java:497)
> at org.jboss.forge.addon.ui.impl.controller.WizardCommandControllerImpl.validate(WizardCommandControllerImpl.java:214)
> at org.jboss.forge.addon.ui.impl.controller.NoUIWizardControllerDecorator.validate(NoUIWizardControllerDecorator.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
> at org.jboss.forge.addon.ui.controller.CommandController_$$_javassist_c9e95bc0-f945-4ada-ae34-ecb5817baed3.validate(CommandController_$$_javassist_c9e95bc0-f945-4ada-ae34-ecb5817baed3.java)
> at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardPage.validatePage(ForgeWizardPage.java:238)
> at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardPage.access$5(ForgeWizardPage.java:233)
> at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardPage$1$1.run(ForgeWizardPage.java:180)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 58 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months