[JBoss JIRA] (FORGE-1733) Distinguish between similarly named parameters in Shell commands
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1733?page=com.atlassian.jira.plugin... ]
George Gastaldi reassigned FORGE-1733:
--------------------------------------
Assignee: George Gastaldi
> Distinguish between similarly named parameters in Shell commands
> ----------------------------------------------------------------
>
> Key: FORGE-1733
> URL: https://issues.jboss.org/browse/FORGE-1733
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell
> Affects Versions: 2.3.0.Final
> Reporter: Vineet Reynolds
> Assignee: George Gastaldi
>
> When I run this sequence of commands:
> {noformat}
> [tmp]$ project-new --named helloforge
> ***SUCCESS*** Project named 'helloforge' has been created.
> [helloforge]$ scaffold-setup --provider
> Eclipse Link Infinispan Java EE OpenJPA Hibernate
> {noformat}
> I do not see the scaffold providers listed. I instead see the JPA providers. Both of these have the same parameter name in the shell: {{provider}}. The scaffold providers are shown only after I explicitly run {{jpa-setup}}:
> {noformat}
> [helloforge]$ jpa-setup --provider Hibernate --container JBOSS_EAP6
> ***SUCCESS*** Persistence (JPA) is installed.
> [helloforge]$ scaffold-setup --provider
> Faces AngularJS
> {noformat}
> Obviously this is confusing when I expect to see scaffold providers, which during installation can handle JPA setup.
> We could perhaps solve this by allowing the clients to rename parameter names when composing multiple such commands or navigation results from existing commands:
> {noformat}
> <vineetreynolds> We should allow these composite commands to rename parameters of the individual ones
> <vineetreynolds> somehow
> <gastaldi> Hmm
> <vineetreynolds> That way they'd be consistent
> <gastaldi> Not sure we can do that automatically
> <vineetreynolds> yeah
> <gastaldi> There are semantics involved
> <gastaldi> I think the best is to rename the parameter
> <vineetreynolds> It should be in some metadata provided by the composite command
> <gastaldi> Hmmm perhaps
> <vineetreynolds> We should assume that the composite command was written by someone who cannot change the original command
> <gastaldi> Right
> <vineetreynolds> Some callback to override parameter names might help
> <gastaldi> Yeah
> <vineetreynolds> Perhaps we could build it into NavigationResultBuilder
> <gastaldi> Like @AttributeOverrides in JPA
> <vineetreynolds> hmm yeah
> <gastaldi> But the NRB should know the conflicting parameters beforehand?
> <gastaldi> Hummm
> <vineetreynolds> it would be supplied by the client
> <gastaldi> Maybe yes
> <gastaldi> Yes
> <vineetreynolds> s/would/must
> {noformat}
--
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
10 years, 3 months
[JBoss JIRA] (FORGE-1733) Distinguish between similarly named parameters in Shell commands
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1733?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1733:
-----------------------------------
Fix Version/s: 2.x Future
> Distinguish between similarly named parameters in Shell commands
> ----------------------------------------------------------------
>
> Key: FORGE-1733
> URL: https://issues.jboss.org/browse/FORGE-1733
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell
> Affects Versions: 2.3.0.Final
> Reporter: Vineet Reynolds
> Assignee: George Gastaldi
> Fix For: 2.x Future
>
>
> When I run this sequence of commands:
> {noformat}
> [tmp]$ project-new --named helloforge
> ***SUCCESS*** Project named 'helloforge' has been created.
> [helloforge]$ scaffold-setup --provider
> Eclipse Link Infinispan Java EE OpenJPA Hibernate
> {noformat}
> I do not see the scaffold providers listed. I instead see the JPA providers. Both of these have the same parameter name in the shell: {{provider}}. The scaffold providers are shown only after I explicitly run {{jpa-setup}}:
> {noformat}
> [helloforge]$ jpa-setup --provider Hibernate --container JBOSS_EAP6
> ***SUCCESS*** Persistence (JPA) is installed.
> [helloforge]$ scaffold-setup --provider
> Faces AngularJS
> {noformat}
> Obviously this is confusing when I expect to see scaffold providers, which during installation can handle JPA setup.
> We could perhaps solve this by allowing the clients to rename parameter names when composing multiple such commands or navigation results from existing commands:
> {noformat}
> <vineetreynolds> We should allow these composite commands to rename parameters of the individual ones
> <vineetreynolds> somehow
> <gastaldi> Hmm
> <vineetreynolds> That way they'd be consistent
> <gastaldi> Not sure we can do that automatically
> <vineetreynolds> yeah
> <gastaldi> There are semantics involved
> <gastaldi> I think the best is to rename the parameter
> <vineetreynolds> It should be in some metadata provided by the composite command
> <gastaldi> Hmmm perhaps
> <vineetreynolds> We should assume that the composite command was written by someone who cannot change the original command
> <gastaldi> Right
> <vineetreynolds> Some callback to override parameter names might help
> <gastaldi> Yeah
> <vineetreynolds> Perhaps we could build it into NavigationResultBuilder
> <gastaldi> Like @AttributeOverrides in JPA
> <vineetreynolds> hmm yeah
> <gastaldi> But the NRB should know the conflicting parameters beforehand?
> <gastaldi> Hummm
> <vineetreynolds> it would be supplied by the client
> <gastaldi> Maybe yes
> <gastaldi> Yes
> <vineetreynolds> s/would/must
> {noformat}
--
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
10 years, 3 months
[JBoss JIRA] (FORGE-1733) Distinguish between similarly named parameters in Shell commands
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGE-1733?page=com.atlassian.jira.plugin... ]
Vineet Reynolds updated FORGE-1733:
-----------------------------------
Description:
When I run this sequence of commands:
{noformat}
[tmp]$ project-new --named helloforge
***SUCCESS*** Project named 'helloforge' has been created.
[helloforge]$ scaffold-setup --provider
Eclipse Link Infinispan Java EE OpenJPA Hibernate
{noformat}
I do not see the scaffold providers listed. I instead see the JPA providers. Both of these have the same parameter name in the shell: {{provider}}. The scaffold providers are shown only after I explicitly run {{jpa-setup}}:
{noformat}
[helloforge]$ jpa-setup --provider Hibernate --container JBOSS_EAP6
***SUCCESS*** Persistence (JPA) is installed.
[helloforge]$ scaffold-setup --provider
Faces AngularJS
{noformat}
Obviously this is confusing when I expect to see scaffold providers, which during installation can handle JPA setup.
We could perhaps solve this by allowing the clients to rename parameter names when composing multiple such commands or navigation results from existing commands:
{noformat}
<vineetreynolds> We should allow these composite commands to rename parameters of the individual ones
<vineetreynolds> somehow
<gastaldi> Hmm
<vineetreynolds> That way they'd be consistent
<gastaldi> Not sure we can do that automatically
<vineetreynolds> yeah
<gastaldi> There are semantics involved
<gastaldi> I think the best is to rename the parameter
<vineetreynolds> It should be in some metadata provided by the composite command
<gastaldi> Hmmm perhaps
<vineetreynolds> We should assume that the composite command was written by someone who cannot change the original command
<gastaldi> Right
<vineetreynolds> Some callback to override parameter names might help
<gastaldi> Yeah
<vineetreynolds> Perhaps we could build it into NavigationResultBuilder
<gastaldi> Like @AttributeOverrides in JPA
<vineetreynolds> hmm yeah
<gastaldi> But the NRB should know the conflicting parameters beforehand?
<gastaldi> Hummm
<vineetreynolds> it would be supplied by the client
<gastaldi> Maybe yes
<gastaldi> Yes
<vineetreynolds> s/would/must
{noformat}
was:
When I run this sequence of commands:
{noformat}
[tmp]$ project-new --named helloforge
***SUCCESS*** Project named 'helloforge' has been created.
[helloforge]$ scaffold-setup --provider
Eclipse Link Infinispan Java EE OpenJPA Hibernate
{noformat}
I do not see the scaffold providers listed. I instead see the JPA providers. Both of these have the same parameter name in the shell: {{provider}}. The scaffold providers are shown only after I explicitly run {{jpa-setup}}:
{noformat}
[helloforge]$ jpa-setup --provider Hibernate --container JBOSS_EAP6
***SUCCESS*** Persistence (JPA) is installed.
[helloforge]$ scaffold-setup --provider
Faces AngularJS
{noformat}
Obviously this is confusing when I expect to see scaffold providers, which during installation can handle JPA setup.
> Distinguish between similarly named parameters in Shell commands
> ----------------------------------------------------------------
>
> Key: FORGE-1733
> URL: https://issues.jboss.org/browse/FORGE-1733
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell
> Affects Versions: 2.3.0.Final
> Reporter: Vineet Reynolds
>
> When I run this sequence of commands:
> {noformat}
> [tmp]$ project-new --named helloforge
> ***SUCCESS*** Project named 'helloforge' has been created.
> [helloforge]$ scaffold-setup --provider
> Eclipse Link Infinispan Java EE OpenJPA Hibernate
> {noformat}
> I do not see the scaffold providers listed. I instead see the JPA providers. Both of these have the same parameter name in the shell: {{provider}}. The scaffold providers are shown only after I explicitly run {{jpa-setup}}:
> {noformat}
> [helloforge]$ jpa-setup --provider Hibernate --container JBOSS_EAP6
> ***SUCCESS*** Persistence (JPA) is installed.
> [helloforge]$ scaffold-setup --provider
> Faces AngularJS
> {noformat}
> Obviously this is confusing when I expect to see scaffold providers, which during installation can handle JPA setup.
> We could perhaps solve this by allowing the clients to rename parameter names when composing multiple such commands or navigation results from existing commands:
> {noformat}
> <vineetreynolds> We should allow these composite commands to rename parameters of the individual ones
> <vineetreynolds> somehow
> <gastaldi> Hmm
> <vineetreynolds> That way they'd be consistent
> <gastaldi> Not sure we can do that automatically
> <vineetreynolds> yeah
> <gastaldi> There are semantics involved
> <gastaldi> I think the best is to rename the parameter
> <vineetreynolds> It should be in some metadata provided by the composite command
> <gastaldi> Hmmm perhaps
> <vineetreynolds> We should assume that the composite command was written by someone who cannot change the original command
> <gastaldi> Right
> <vineetreynolds> Some callback to override parameter names might help
> <gastaldi> Yeah
> <vineetreynolds> Perhaps we could build it into NavigationResultBuilder
> <gastaldi> Like @AttributeOverrides in JPA
> <vineetreynolds> hmm yeah
> <gastaldi> But the NRB should know the conflicting parameters beforehand?
> <gastaldi> Hummm
> <vineetreynolds> it would be supplied by the client
> <gastaldi> Maybe yes
> <gastaldi> Yes
> <vineetreynolds> s/would/must
> {noformat}
--
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
10 years, 3 months
[JBoss JIRA] (FORGE-1733) Distinguish between similarly named parameters in Shell commands
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGE-1733?page=com.atlassian.jira.plugin... ]
Vineet Reynolds updated FORGE-1733:
-----------------------------------
Description:
When I run this sequence of commands:
{noformat}
[tmp]$ project-new --named helloforge
***SUCCESS*** Project named 'helloforge' has been created.
[helloforge]$ scaffold-setup --provider
Eclipse Link Infinispan Java EE OpenJPA Hibernate
{noformat}
I do not see the scaffold providers listed. I instead see the JPA providers. Both of these have the same parameter name in the shell: {{provider}}. The scaffold providers are shown only after I explicitly run {{jpa-setup}}:
{noformat}
[helloforge]$ jpa-setup --provider Hibernate --container JBOSS_EAP6
***SUCCESS*** Persistence (JPA) is installed.
[helloforge]$ scaffold-setup --provider
Faces AngularJS
{noformat}
Obviously this is confusing when I expect to see scaffold providers, which during installation can handle JPA setup.
was:
When I run this sequence of commands:
{noformat}
[tmp]$ project-new --named helloforge
***SUCCESS*** Project named 'helloforge' has been created.
[helloforge]$ scaffold-setup --provider
Eclipse Link Infinispan Java EE OpenJPA Hibernate
{noformat}
I do not see the scaffold providers listed. I instead see the JPA providers. Both of these have the same parameter name in the shell: {{provider}}. The scaffold providers are shown only after I explicitly run {{jpa-setup}}. Obviously this is confusing when I expect to see scaffold providers, which during installation can handle JPA setup.
> Distinguish between similarly named parameters in Shell commands
> ----------------------------------------------------------------
>
> Key: FORGE-1733
> URL: https://issues.jboss.org/browse/FORGE-1733
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell
> Affects Versions: 2.3.0.Final
> Reporter: Vineet Reynolds
>
> When I run this sequence of commands:
> {noformat}
> [tmp]$ project-new --named helloforge
> ***SUCCESS*** Project named 'helloforge' has been created.
> [helloforge]$ scaffold-setup --provider
> Eclipse Link Infinispan Java EE OpenJPA Hibernate
> {noformat}
> I do not see the scaffold providers listed. I instead see the JPA providers. Both of these have the same parameter name in the shell: {{provider}}. The scaffold providers are shown only after I explicitly run {{jpa-setup}}:
> {noformat}
> [helloforge]$ jpa-setup --provider Hibernate --container JBOSS_EAP6
> ***SUCCESS*** Persistence (JPA) is installed.
> [helloforge]$ scaffold-setup --provider
> Faces AngularJS
> {noformat}
> Obviously this is confusing when I expect to see scaffold providers, which during installation can handle JPA setup.
--
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
10 years, 3 months
[JBoss JIRA] (FORGE-1733) Distinguish between similarly named parameters in Shell commands
by Vineet Reynolds (JIRA)
Vineet Reynolds created FORGE-1733:
--------------------------------------
Summary: Distinguish between similarly named parameters in Shell commands
Key: FORGE-1733
URL: https://issues.jboss.org/browse/FORGE-1733
Project: Forge
Issue Type: Feature Request
Components: UI - Shell
Affects Versions: 2.3.0.Final
Reporter: Vineet Reynolds
When I run this sequence of commands:
{noformat}
[tmp]$ project-new --named helloforge
***SUCCESS*** Project named 'helloforge' has been created.
[helloforge]$ scaffold-setup --provider
Eclipse Link Infinispan Java EE OpenJPA Hibernate
{noformat}
I do not see the scaffold providers listed. I instead see the JPA providers. Both of these have the same parameter name in the shell: {{provider}}. The scaffold providers are shown only after I explicitly run {{jpa-setup}}. Obviously this is confusing when I expect to see scaffold providers, which during installation can handle JPA setup.
--
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
10 years, 3 months
[JBoss JIRA] (FORGE-1626) Install addon from git repository
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1626?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1626.
----------------------------------
Assignee: George Gastaldi
Fix Version/s: 2.4.0.Final
Resolution: Done
> Install addon from git repository
> ---------------------------------
>
> Key: FORGE-1626
> URL: https://issues.jboss.org/browse/FORGE-1626
> Project: Forge
> Issue Type: Feature Request
> Components: Addon Manager
> Affects Versions: 2.x Future
> Reporter: Ivan St. Ivanov
> Assignee: George Gastaldi
> Fix For: 2.4.0.Final
>
>
> Forge should be able to install addons from a remote [git] repository.
> In order to do that, Forge will have to first download the addon sources, then build it and finally install the built artifact.
> Remark: There is already git-tools addon that can be used for pulling the sources.
--
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
10 years, 3 months
[JBoss JIRA] (FORGE-1731) Exception when running scaffold-generate before scaffold-setup
by Lincoln Baxter III (JIRA)
Lincoln Baxter III created FORGE-1731:
-----------------------------------------
Summary: Exception when running scaffold-generate before scaffold-setup
Key: FORGE-1731
URL: https://issues.jboss.org/browse/FORGE-1731
Project: Forge
Issue Type: Bug
Components: Scaffold
Reporter: Lincoln Baxter III
In eclipse wizards:
project-new --named something
scaffold-setup (error ensues)
{code}
SEVERE: Error while navigating to next step
org.jboss.forge.addon.facets.FacetNotFoundException: No Facet of type [interface org.jboss.forge.addon.javaee.jpa.JPAFacet] is installed.
at org.jboss.forge.addon.facets.AbstractFaceted.getFacet(AbstractFaceted.java:51)
at org.jboss.forge.addon.scaffold.faces.ScaffoldableEntitySelectionWizard.initializeUI(ScaffoldableEntitySelectionWizard.java:110)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:59)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:75)
at org.jboss.forge.addon.scaffold.faces.ScaffoldableEntitySelectionWizard_$$_javassist_019006e3-4b9f-479f-bacc-eacf38dab5be.initializeUI(ScaffoldableEntitySelectionWizard_$$_javassist_019006e3-4b9f-479f-bacc-eacf38dab5be.java)
at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.initialize(SingleCommandControllerImpl.java:55)
at org.jboss.forge.addon.ui.impl.controller.WizardCommandControllerImpl.initialize(WizardCommandControllerImpl.java:114)
at org.jboss.forge.addon.ui.impl.controller.NoUIWizardControllerDecorator.canMoveToNextStep(NoUIWizardControllerDecorator.java:60)
at sun.reflect.GeneratedMethodAccessor130.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$1.call(ClassLoaderAdapterCallback.java:98)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:71)
at org.jboss.forge.addon.ui.controller.CommandController_$$_javassist_3ca44b11-b13f-4587-a0ae-753e02b250f4.canMoveToNextStep(CommandController_$$_javassist_3ca44b11-b13f-4587-a0ae-753e02b250f4.java)
at org.jboss.tools.forge.ui.ext.wizards.ForgeWizardPage.canFlipToNextPage(ForgeWizardPage.java:234)
at org.eclipse.jface.wizard.WizardDialog.updateButtons(WizardDialog.java:1349)
at org.jboss.tools.forge.ui.ext.wizards.ForgeWizardPage.handleEvent(ForgeWizardPage.java:147)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
at org.eclipse.jface.window.Window.open(Window.java:802)
at org.jboss.tools.forge.ui.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:157)
at org.jboss.tools.forge.ui.ext.dialog.UICommandListDialog$1$1.handleElementSelected(UICommandListDialog.java:161)
at org.jboss.tools.forge.ui.ext.quickaccess.QuickAccessContents.handleSelection(QuickAccessContents.java:326)
at org.jboss.tools.forge.ui.ext.quickaccess.QuickAccessContents.access$0(QuickAccessContents.java:316)
at org.jboss.tools.forge.ui.ext.quickaccess.QuickAccessContents$1.keyPressed(QuickAccessContents.java:347)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:167)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1503)
at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1632)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1499)
at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1598)
at org.eclipse.swt.widgets.Control.doCommandBySelector(Control.java:1060)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5648)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
at org.eclipse.swt.widgets.Widget.superKeyDown(Widget.java:1907)
at org.eclipse.swt.widgets.Widget.keyDown(Widget.java:1085)
at org.eclipse.swt.widgets.Control.keyDown(Control.java:2400)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5558)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2104)
at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2318)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5620)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5057)
at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5206)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3648)
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:140)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611)
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:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
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
10 years, 3 months
[JBoss JIRA] (FORGE-1728) ClassCastException when a wizard is invoked in Eclipse plugin
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1728?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III closed FORGE-1728.
-------------------------------------
Resolution: Done
> ClassCastException when a wizard is invoked in Eclipse plugin
> -------------------------------------------------------------
>
> Key: FORGE-1728
> URL: https://issues.jboss.org/browse/FORGE-1728
> Project: Forge
> Issue Type: Bug
> Components: Furnace (Container), Furnace CDI, Furnace Simple, UI - Eclipse
> Reporter: George Gastaldi
> Assignee: Lincoln Baxter III
> Priority: Blocker
> Fix For: 2.4.0.Final
>
>
> It doesn't happen with Furnace 2.3.0.Final, so I guess it was some change introduced in 2.3.1-SNAPSHOT
> {code}
> java.lang.ClassCastException: org.jboss.forge.addon.facets.AbstractFaceted_$$_javassist_8b700113-c96b-430a-9ecc-38c496ae6505 cannot be cast to org.jboss.forge.addon.ui.input.InputComponent
> at org.jboss.tools.forge.ui.ext.wizards.ForgeWizardPage.createControl(ForgeWizardPage.java:85)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
> at org.eclipse.jface.window.Window.create(Window.java:432)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
> at org.eclipse.jface.window.Window.open(Window.java:791)
> at org.jboss.tools.forge.ui.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:157)
> at org.jboss.tools.forge.ui.ext.dialog.UICommandListDialog$1$1.handleElementSelected(UICommandListDialog.java:161)
> at org.jboss.tools.forge.ui.ext.quickaccess.QuickAccessContents.handleSelection(QuickAccessContents.java:326)
> at org.jboss.tools.forge.ui.ext.quickaccess.QuickAccessContents.access$0(QuickAccessContents.java:316)
> at org.jboss.tools.forge.ui.ext.quickaccess.QuickAccessContents$6.mouseUp(QuickAccessContents.java:465)
> 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.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:140)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611)
> 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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 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
10 years, 3 months