April 2014 - forge-issues - Jboss List Archives

[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 reassigned FORGE-1728: ----------------------------------------- Assignee: Lincoln Baxter III > 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1730) Move git addon to core

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1730?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1730. ---------------------------------- Resolution: Done > Move git addon to core > ---------------------- > > Key: FORGE-1730 > URL: https://issues.jboss.org/browse/FORGE-1730 > Project: Forge > Issue Type: Task > Components: Git > Affects Versions: 2.3.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.4.0.Final > > -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1730) Move git addon to core

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1730?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1730: ----------------------------------- Component/s: Git > Move git addon to core > ---------------------- > > Key: FORGE-1730 > URL: https://issues.jboss.org/browse/FORGE-1730 > Project: Forge > Issue Type: Task > Components: Git > Affects Versions: 2.3.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.4.0.Final > > -- 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

1
0
0 / 0

[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 commented on FORGE-1626: ---------------------------------------- this should be in the addon-manager and optionally depend on the git addon > 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 > > 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1730) Move git addon to core

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1730: -------------------------------------- Summary: Move git addon to core Key: FORGE-1730 URL: https://issues.jboss.org/browse/FORGE-1730 Project: Forge Issue Type: Task Affects Versions: 2.3.0.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.4.0.Final -- 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

1
0
0 / 0

[JBoss JIRA] (ROASTER-5) Having method parameters a bit more typed

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/ROASTER-5?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on ROASTER-5: --------------------------------------- {{addParameter()}} should return the just added Parameter object, so I guess the code would be like: {code} MethodSource<?> method = javaClass.addMethod().setPublic().setName("isValid").setReturnType("boolean"); method.addParameter(Number.class, "value"); method.addParameter(ConstraintValidatorContext.class, "context"); method.setBody("return false;").addAnnotation(Override.class); {code} > Having method parameters a bit more typed > ----------------------------------------- > > Key: ROASTER-5 > URL: https://issues.jboss.org/browse/ROASTER-5 > Project: Roaster > Issue Type: Feature Request > Components: API > Affects Versions: 2.1.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > I want to create a Bean Validation implementation, that means that the {{isValid}} method takes two parameters. And the only way to add two parameters seems to be by a String > {code} > javaClass.addMethod().setPublic().setName("isValid").setReturnType("boolean").setParameters("Number value, ConstraintValidatorContext context").setBody("return false;").addAnnotation(Override.class); > {code} > It would be nice to have typed parameters so the import is implicit, and things are a bit more typed : > {code} > javaClass.addMethod().setPublic().setName("isValid").setReturnType("boolean").addParameter(Number.class, "value").addParameter(ConstraintValidatorContext.class, "context").setBody("return false;").addAnnotation(Override.class); > {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

1
0
0 / 0

[JBoss JIRA] (FORGE-1729) Test harness should set the Configuration directory to use the test temp dir by default

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1729?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1729: ---------------------------------------- You need to add the following code to your test class {code} static { ConfigurationFactoryImpl.setupTemporaryUserConfig(); } {code} > Test harness should set the Configuration directory to use the test temp dir by default > --------------------------------------------------------------------------------------- > > Key: FORGE-1729 > URL: https://issues.jboss.org/browse/FORGE-1729 > Project: Forge > Issue Type: Enhancement > Components: Configuration > Affects Versions: 2.3.0.Final > Reporter: Lincoln Baxter III > Fix For: 2.4.0.Final > > > Currently the UserConfiguration references the current users home directory while running tests - it should use the available system property while running tests in order to direct the config dir to a temp location for that test execution: > {code} > static final String USER_CONFIG_PATH = "org.jboss.forge.addon.configuration.USER_CONFIG_PATH"; > String property = System.getProperty(USER_CONFIG_PATH);{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

1
0
0 / 0

[JBoss JIRA] (FORGE-1729) Test harness should set the Configuration directory to use the test temp dir by default

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1729?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1729: -------------------------------------- Component/s: Configuration > Test harness should set the Configuration directory to use the test temp dir by default > --------------------------------------------------------------------------------------- > > Key: FORGE-1729 > URL: https://issues.jboss.org/browse/FORGE-1729 > Project: Forge > Issue Type: Enhancement > Components: Configuration > Reporter: Lincoln Baxter III > > Currently the UserConfiguration references the current users home directory while running tests - it should use the available system property while running tests in order to direct the config dir to a temp location for that test execution: > {code} > static final String USER_CONFIG_PATH = "org.jboss.forge.addon.configuration.USER_CONFIG_PATH"; > String property = System.getProperty(USER_CONFIG_PATH);{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

1
0
0 / 0

[JBoss JIRA] (FORGE-1729) Test harness should set the Configuration directory to use the test temp dir by default

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1729: ----------------------------------------- Summary: Test harness should set the Configuration directory to use the test temp dir by default Key: FORGE-1729 URL: https://issues.jboss.org/browse/FORGE-1729 Project: Forge Issue Type: Enhancement Reporter: Lincoln Baxter III Currently the UserConfiguration references the current users home directory while running tests - it should use the available system property while running tests in order to direct the config dir to a temp location for that test execution: {code} static final String USER_CONFIG_PATH = "org.jboss.forge.addon.configuration.USER_CONFIG_PATH"; String property = System.getProperty(USER_CONFIG_PATH);{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

1
0
0 / 0

[JBoss JIRA] (FORGE-1729) Test harness should set the Configuration directory to use the test temp dir by default

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1729?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1729: -------------------------------------- Affects Version/s: 2.3.0.Final > Test harness should set the Configuration directory to use the test temp dir by default > --------------------------------------------------------------------------------------- > > Key: FORGE-1729 > URL: https://issues.jboss.org/browse/FORGE-1729 > Project: Forge > Issue Type: Enhancement > Components: Configuration > Affects Versions: 2.3.0.Final > Reporter: Lincoln Baxter III > > Currently the UserConfiguration references the current users home directory while running tests - it should use the available system property while running tests in order to direct the config dir to a temp location for that test execution: > {code} > static final String USER_CONFIG_PATH = "org.jboss.forge.addon.configuration.USER_CONFIG_PATH"; > String property = System.getProperty(USER_CONFIG_PATH);{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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues April 2014