April 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1738) addon-git-install fails to install projects from git if the project is not available in any configured maven repository

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1738: -------------------------------------- Summary: addon-git-install fails to install projects from git if the project is not available in any configured maven repository Key: FORGE-1738 URL: https://issues.jboss.org/browse/FORGE-1738 Project: Forge Issue Type: Bug Components: Addon Manager, Maven Affects Versions: 2.4.1.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.4.2.Final The Furnace maven plugin tries to generate the DOT file but fails to resolve from the current maven build. The solution is to skip DOT generation using {{-Dfurnace.dot.skip=true}} when installing the addon locally -- 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-1736) Upgrade to Aesh 0.52

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1736?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1736. ---------------------------------- Resolution: Done > Upgrade to Aesh 0.52 > -------------------- > > Key: FORGE-1736 > URL: https://issues.jboss.org/browse/FORGE-1736 > Project: Forge > Issue Type: Component Upgrade > Components: UI - Shell > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.4.1.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-1737) Upgrade to Roaster 2.1.0.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1737?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1737. ---------------------------------- Resolution: Done > Upgrade to Roaster 2.1.0.Final > ------------------------------ > > Key: FORGE-1737 > URL: https://issues.jboss.org/browse/FORGE-1737 > Project: Forge > Issue Type: Component Upgrade > Components: Parsers / File Manipulation > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.4.1.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-1737) Upgrade to Roaster 2.1.0.Final

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1737: -------------------------------------- Summary: Upgrade to Roaster 2.1.0.Final Key: FORGE-1737 URL: https://issues.jboss.org/browse/FORGE-1737 Project: Forge Issue Type: Component Upgrade Components: Parsers / File Manipulation Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.4.1.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-1736) Upgrade to Aesh 0.52

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1736: -------------------------------------- Summary: Upgrade to Aesh 0.52 Key: FORGE-1736 URL: https://issues.jboss.org/browse/FORGE-1736 Project: Forge Issue Type: Component Upgrade Components: UI - Shell Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.4.1.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-1715) Migrate Property used in Validation/constraint support in JavaEE to Roaster

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1715?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1715. ---------------------------------- Resolution: Done > Migrate Property used in Validation/constraint support in JavaEE to Roaster > --------------------------------------------------------------------------- > > Key: FORGE-1715 > URL: https://issues.jboss.org/browse/FORGE-1715 > Project: Forge > Issue Type: Enhancement > Components: Java EE > Affects Versions: 2.3.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.4.1.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-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 updated FORGE-1729: ----------------------------------- Fix Version/s: 2.x Future (was: 2.4.1.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 > Fix For: 2.x Future > > > 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-1735) No commands are displayed sporadically

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1735?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reassigned FORGE-1735: ----------------------------------------- Assignee: Lincoln Baxter III > No commands are displayed sporadically > -------------------------------------- > > Key: FORGE-1735 > URL: https://issues.jboss.org/browse/FORGE-1735 > Project: Forge > Issue Type: Bug > Components: Furnace (Container), Furnace CDI, Furnace Simple > Affects Versions: 2.3.0.Final > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Priority: Critical > Fix For: 2.x Future > > > Sometimes the command list in Eclipse (or Shell) appears empty when invoked. > By debugging, found out that the problem lies in the instanceCaches in ImportedImpl and in the ServiceRegistry implementations. For some reason they are empty (perhaps invoked prematurely?) and it never queries the services back. By cleaning the instanceCache on debug fixed the issue -- 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-1735) No commands are displayed sporadically

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1735?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1735. ------------------------------------- Fix Version/s: 2.4.0.Final (was: 2.x Future) Resolution: Done Added missing isEmpty() check to caches. > No commands are displayed sporadically > -------------------------------------- > > Key: FORGE-1735 > URL: https://issues.jboss.org/browse/FORGE-1735 > Project: Forge > Issue Type: Bug > Components: Furnace (Container), Furnace CDI, Furnace Simple > Affects Versions: 2.3.0.Final > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Priority: Critical > Fix For: 2.4.0.Final > > > Sometimes the command list in Eclipse (or Shell) appears empty when invoked. > By debugging, found out that the problem lies in the instanceCaches in ImportedImpl and in the ServiceRegistry implementations. For some reason they are empty (perhaps invoked prematurely?) and it never queries the services back. By cleaning the instanceCache on debug fixed the issue -- 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-1734) CCE when starting up the integrated Forge console in JBT

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1734?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1734. ------------------------------------- Resolution: Done Fixed. > CCE when starting up the integrated Forge console in JBT > -------------------------------------------------------- > > Key: FORGE-1734 > URL: https://issues.jboss.org/browse/FORGE-1734 > Project: Forge > Issue Type: Bug > Components: Furnace (Container) > Reporter: Koen Aers > Assignee: Lincoln Baxter III > Fix For: 2.4.0.Final > > > This is the stack trace that results: > !ENTRY org.eclipse.ui 4 0 2014-04-04 17:04:12.441 > !MESSAGE Unhandled event loop exception > !STACK 0 > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.ClassCastException: org.jboss.forge.furnace.proxy.ForgeProxy_$$_javassist_e30dba7a-ee9b-437c-9b4d-ee8a2a5ac750 cannot be cast to org.jboss.forge.addon.shell.ShellHandle) > at org.eclipse.swt.SWT.error(SWT.java:4441) > at org.eclipse.swt.SWT.error(SWT.java:4356) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:139) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3978) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3655) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:147) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:630) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:574) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:133) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:103) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:378) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:232) > 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:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1462) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > Caused by: java.lang.ClassCastException: org.jboss.forge.furnace.proxy.ForgeProxy_$$_javassist_e30dba7a-ee9b-437c-9b4d-ee8a2a5ac750 cannot be cast to org.jboss.forge.addon.shell.ShellHandle > at org.jboss.tools.forge.ui.ext.cli.F2Console.start(F2Console.java:19) > at org.jboss.tools.aesh.ui.view.AeshTextViewer$3.run(AeshTextViewer.java:79) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) > ... 24 more -- 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