[JBoss JIRA] (FORGE-2580) Stack field should be disabled for certain project types
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2580?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-2580:
----------------------------------------
Hi [~davsclaus],
Can you test against the latest master? I'll release Forge 3.0.0.Beta3 today if that works for you.
Thanks!
> Stack field should be disabled for certain project types
> --------------------------------------------------------
>
> Key: FORGE-2580
> URL: https://issues.jboss.org/browse/FORGE-2580
> Project: Forge
> Issue Type: Task
> Affects Versions: 3.0.0.Beta2
> Reporter: Claus Ibsen
> Assignee: George Gastaldi
> Fix For: 3.0.0.Beta3
>
>
> In beta2 the project-new command now asks about build system (see below).
> Because its JEE related asking about JEE6 and JEE7 what does it do? And is there a way to turn it off. Its IMHO important for forge to be "neutral" and not impose something like JEE on users that do not want this.
> As I chose from archetype / archetype-catalog. I just want project-new to create the maven project 100% from the maven archetype and not do "extra stuff" about JEE.
> {code}
> [workspace]$ project-new
> ***INFO*** Required inputs not satisfied, entering interactive mode
> * Project name: foo
> ? Top level package [org.foo]:
> ? Version [1.0.0-SNAPSHOT]:
> ? Final name:
> ? Project location [/Users/davsclaus/Documents/workspace]:
> [0] (x) war
> [1] ( ) jar
> [2] ( ) parent
> [3] ( ) addon
> [4] ( ) resource-jar
> [5] ( ) ear
> [6] ( ) from-archetype
> [7] ( ) from-archetype-catalog
> [8] ( ) generic
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> * Project type: [0-8] 7
> [0] (x) Maven
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> * Build system: [0] 0
> [0] ( ) JAVA_EE_7
> [1] ( ) JAVA_EE_6
> [2] ( ) NONE
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? Stack (The technology stack to be used in this project): [0-2] 2
> [0] ( ) camel
> [1] ( ) fabric8
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (FORGE-2580) Stack field should be disabled for certain project types
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2580?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-2580:
-----------------------------------
Fix Version/s: 3.0.0.Beta3
> Stack field should be disabled for certain project types
> --------------------------------------------------------
>
> Key: FORGE-2580
> URL: https://issues.jboss.org/browse/FORGE-2580
> Project: Forge
> Issue Type: Task
> Affects Versions: 3.0.0.Beta2
> Reporter: Claus Ibsen
> Fix For: 3.0.0.Beta3
>
>
> In beta2 the project-new command now asks about build system (see below).
> Because its JEE related asking about JEE6 and JEE7 what does it do? And is there a way to turn it off. Its IMHO important for forge to be "neutral" and not impose something like JEE on users that do not want this.
> As I chose from archetype / archetype-catalog. I just want project-new to create the maven project 100% from the maven archetype and not do "extra stuff" about JEE.
> {code}
> [workspace]$ project-new
> ***INFO*** Required inputs not satisfied, entering interactive mode
> * Project name: foo
> ? Top level package [org.foo]:
> ? Version [1.0.0-SNAPSHOT]:
> ? Final name:
> ? Project location [/Users/davsclaus/Documents/workspace]:
> [0] (x) war
> [1] ( ) jar
> [2] ( ) parent
> [3] ( ) addon
> [4] ( ) resource-jar
> [5] ( ) ear
> [6] ( ) from-archetype
> [7] ( ) from-archetype-catalog
> [8] ( ) generic
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> * Project type: [0-8] 7
> [0] (x) Maven
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> * Build system: [0] 0
> [0] ( ) JAVA_EE_7
> [1] ( ) JAVA_EE_6
> [2] ( ) NONE
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? Stack (The technology stack to be used in this project): [0-2] 2
> [0] ( ) camel
> [1] ( ) fabric8
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (FORGE-2580) Stack field should be disabled for certain project types
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2580?page=com.atlassian.jira.plugin... ]
George Gastaldi reassigned FORGE-2580:
--------------------------------------
Assignee: George Gastaldi
> Stack field should be disabled for certain project types
> --------------------------------------------------------
>
> Key: FORGE-2580
> URL: https://issues.jboss.org/browse/FORGE-2580
> Project: Forge
> Issue Type: Task
> Affects Versions: 3.0.0.Beta2
> Reporter: Claus Ibsen
> Assignee: George Gastaldi
> Fix For: 3.0.0.Beta3
>
>
> In beta2 the project-new command now asks about build system (see below).
> Because its JEE related asking about JEE6 and JEE7 what does it do? And is there a way to turn it off. Its IMHO important for forge to be "neutral" and not impose something like JEE on users that do not want this.
> As I chose from archetype / archetype-catalog. I just want project-new to create the maven project 100% from the maven archetype and not do "extra stuff" about JEE.
> {code}
> [workspace]$ project-new
> ***INFO*** Required inputs not satisfied, entering interactive mode
> * Project name: foo
> ? Top level package [org.foo]:
> ? Version [1.0.0-SNAPSHOT]:
> ? Final name:
> ? Project location [/Users/davsclaus/Documents/workspace]:
> [0] (x) war
> [1] ( ) jar
> [2] ( ) parent
> [3] ( ) addon
> [4] ( ) resource-jar
> [5] ( ) ear
> [6] ( ) from-archetype
> [7] ( ) from-archetype-catalog
> [8] ( ) generic
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> * Project type: [0-8] 7
> [0] (x) Maven
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> * Build system: [0] 0
> [0] ( ) JAVA_EE_7
> [1] ( ) JAVA_EE_6
> [2] ( ) NONE
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? Stack (The technology stack to be used in this project): [0-2] 2
> [0] ( ) camel
> [1] ( ) fabric8
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (FORGE-2580) Stack field should be disabled for Archetype project types
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2580?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-2580:
-----------------------------------
Summary: Stack field should be disabled for Archetype project types (was: project-new - What is the new build system used for?)
> Stack field should be disabled for Archetype project types
> ----------------------------------------------------------
>
> Key: FORGE-2580
> URL: https://issues.jboss.org/browse/FORGE-2580
> Project: Forge
> Issue Type: Task
> Affects Versions: 3.0.0.Beta2
> Reporter: Claus Ibsen
>
> In beta2 the project-new command now asks about build system (see below).
> Because its JEE related asking about JEE6 and JEE7 what does it do? And is there a way to turn it off. Its IMHO important for forge to be "neutral" and not impose something like JEE on users that do not want this.
> As I chose from archetype / archetype-catalog. I just want project-new to create the maven project 100% from the maven archetype and not do "extra stuff" about JEE.
> {code}
> [workspace]$ project-new
> ***INFO*** Required inputs not satisfied, entering interactive mode
> * Project name: foo
> ? Top level package [org.foo]:
> ? Version [1.0.0-SNAPSHOT]:
> ? Final name:
> ? Project location [/Users/davsclaus/Documents/workspace]:
> [0] (x) war
> [1] ( ) jar
> [2] ( ) parent
> [3] ( ) addon
> [4] ( ) resource-jar
> [5] ( ) ear
> [6] ( ) from-archetype
> [7] ( ) from-archetype-catalog
> [8] ( ) generic
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> * Project type: [0-8] 7
> [0] (x) Maven
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> * Build system: [0] 0
> [0] ( ) JAVA_EE_7
> [1] ( ) JAVA_EE_6
> [2] ( ) NONE
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? Stack (The technology stack to be used in this project): [0-2] 2
> [0] ( ) camel
> [1] ( ) fabric8
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (FORGE-2580) Stack field should be disabled for certain project types
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2580?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-2580:
-----------------------------------
Summary: Stack field should be disabled for certain project types (was: Stack field should be disabled for Archetype project types)
> Stack field should be disabled for certain project types
> --------------------------------------------------------
>
> Key: FORGE-2580
> URL: https://issues.jboss.org/browse/FORGE-2580
> Project: Forge
> Issue Type: Task
> Affects Versions: 3.0.0.Beta2
> Reporter: Claus Ibsen
>
> In beta2 the project-new command now asks about build system (see below).
> Because its JEE related asking about JEE6 and JEE7 what does it do? And is there a way to turn it off. Its IMHO important for forge to be "neutral" and not impose something like JEE on users that do not want this.
> As I chose from archetype / archetype-catalog. I just want project-new to create the maven project 100% from the maven archetype and not do "extra stuff" about JEE.
> {code}
> [workspace]$ project-new
> ***INFO*** Required inputs not satisfied, entering interactive mode
> * Project name: foo
> ? Top level package [org.foo]:
> ? Version [1.0.0-SNAPSHOT]:
> ? Final name:
> ? Project location [/Users/davsclaus/Documents/workspace]:
> [0] (x) war
> [1] ( ) jar
> [2] ( ) parent
> [3] ( ) addon
> [4] ( ) resource-jar
> [5] ( ) ear
> [6] ( ) from-archetype
> [7] ( ) from-archetype-catalog
> [8] ( ) generic
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> * Project type: [0-8] 7
> [0] (x) Maven
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> * Build system: [0] 0
> [0] ( ) JAVA_EE_7
> [1] ( ) JAVA_EE_6
> [2] ( ) NONE
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? Stack (The technology stack to be used in this project): [0-2] 2
> [0] ( ) camel
> [1] ( ) fabric8
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (FORGE-2580) project-new - What is the new build system used for?
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2580?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-2580:
----------------------------------------
The new field is called Stack. It is meant to allow the user to choose the stack it wants l. But I agree that it doesn't make much sense when dealing with archetypes. Perhaps it should be enabled only for some specific project types.
> project-new - What is the new build system used for?
> ----------------------------------------------------
>
> Key: FORGE-2580
> URL: https://issues.jboss.org/browse/FORGE-2580
> Project: Forge
> Issue Type: Task
> Affects Versions: 3.0.0.Beta2
> Reporter: Claus Ibsen
>
> In beta2 the project-new command now asks about build system (see below).
> Because its JEE related asking about JEE6 and JEE7 what does it do? And is there a way to turn it off. Its IMHO important for forge to be "neutral" and not impose something like JEE on users that do not want this.
> As I chose from archetype / archetype-catalog. I just want project-new to create the maven project 100% from the maven archetype and not do "extra stuff" about JEE.
> {code}
> [workspace]$ project-new
> ***INFO*** Required inputs not satisfied, entering interactive mode
> * Project name: foo
> ? Top level package [org.foo]:
> ? Version [1.0.0-SNAPSHOT]:
> ? Final name:
> ? Project location [/Users/davsclaus/Documents/workspace]:
> [0] (x) war
> [1] ( ) jar
> [2] ( ) parent
> [3] ( ) addon
> [4] ( ) resource-jar
> [5] ( ) ear
> [6] ( ) from-archetype
> [7] ( ) from-archetype-catalog
> [8] ( ) generic
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> * Project type: [0-8] 7
> [0] (x) Maven
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> * Build system: [0] 0
> [0] ( ) JAVA_EE_7
> [1] ( ) JAVA_EE_6
> [2] ( ) NONE
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? Stack (The technology stack to be used in this project): [0-2] 2
> [0] ( ) camel
> [1] ( ) fabric8
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (FORGE-2580) project-new - What is the new build system used for?
by Claus Ibsen (JIRA)
Claus Ibsen created FORGE-2580:
----------------------------------
Summary: project-new - What is the new build system used for?
Key: FORGE-2580
URL: https://issues.jboss.org/browse/FORGE-2580
Project: Forge
Issue Type: Task
Affects Versions: 3.0.0.Beta2
Reporter: Claus Ibsen
In beta2 the project-new command now asks about build system (see below).
Because its JEE related asking about JEE6 and JEE7 what does it do? And is there a way to turn it off. Its IMHO important for forge to be "neutral" and not impose something like JEE on users that do not want this.
As I chose from archetype / archetype-catalog. I just want project-new to create the maven project 100% from the maven archetype and not do "extra stuff" about JEE.
{code}
[workspace]$ project-new
***INFO*** Required inputs not satisfied, entering interactive mode
* Project name: foo
? Top level package [org.foo]:
? Version [1.0.0-SNAPSHOT]:
? Final name:
? Project location [/Users/davsclaus/Documents/workspace]:
[0] (x) war
[1] ( ) jar
[2] ( ) parent
[3] ( ) addon
[4] ( ) resource-jar
[5] ( ) ear
[6] ( ) from-archetype
[7] ( ) from-archetype-catalog
[8] ( ) generic
Press <ENTER> to confirm, or <CTRL>+C to cancel.
* Project type: [0-8] 7
[0] (x) Maven
Press <ENTER> to confirm, or <CTRL>+C to cancel.
* Build system: [0] 0
[0] ( ) JAVA_EE_7
[1] ( ) JAVA_EE_6
[2] ( ) NONE
Press <ENTER> to confirm, or <CTRL>+C to cancel.
? Stack (The technology stack to be used in this project): [0-2] 2
[0] ( ) camel
[1] ( ) fabric8
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (FORGE-2343) project-new command causes exception in Eclipse
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2343?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-2343.
----------------------------------
Fix Version/s: 3.0.0.Beta2
(was: 3.x Future)
Assignee: George Gastaldi
Resolution: Done
This seems to be resolved in the latest Forge version
> project-new command causes exception in Eclipse
> -----------------------------------------------
>
> Key: FORGE-2343
> URL: https://issues.jboss.org/browse/FORGE-2343
> Project: Forge
> Issue Type: Bug
> Affects Versions: 2.16.0.Final
> Environment: Eclipse Mars with Forge 2.16.0.Final installed
> Reporter: Claus Ibsen
> Assignee: George Gastaldi
> Fix For: 3.0.0.Beta2
>
>
> Using forge project-new and provide some details and it worked the 1st time. When I close the project and create a new project then the command shows a notification that the project was "succesfully" created, but there is no new directory with the project in the file system.
> In the error log in Eclipse I can find this stacktrace
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IndexOutOfBoundsException: Index: 1, 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: 1, 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.GeneratedMethodAccessor617.invoke(Unknown Source)
> 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_8b9474bb-768c-45a0-8ea0-e583ce8a8f33.validate(CommandController_$$_javassist_8b9474bb-768c-45a0-8ea0-e583ce8a8f33.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)
8 years, 11 months