January 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-967) Support CDI qualifiers in AddonRegistry.getExportedInstance methods

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-967?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-967. --------------------------------- Fix Version/s: (was: 2.x Future) Resolution: Won't Fix This concept is not implemented in Furnace because it's CDI specific. Reopen if it is still needed > Support CDI qualifiers in AddonRegistry.getExportedInstance methods > ------------------------------------------------------------------- > > Key: FORGE-967 > URL: https://issues.jboss.org/browse/FORGE-967 > Project: Forge > Issue Type: Feature Request > Components: Furnace (Container) > Affects Versions: 2.0.0.Alpha5 > Reporter: George Gastaldi > -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1113) Need to be able to listen to Exported service events (Service becomes available/unavailable)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1113?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1113: ---------------------------------------- Isn't this achieved by listening to PreShutdown and PostStartup events? > Need to be able to listen to Exported service events (Service becomes available/unavailable) > -------------------------------------------------------------------------------------------- > > Key: FORGE-1113 > URL: https://issues.jboss.org/browse/FORGE-1113 > Project: Forge > Issue Type: Feature Request > Components: Furnace (Container) > Affects Versions: 2.0.0.Alpha10 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1335) Creating new project, JVM IBM 1.7

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1335?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1335: ---------------------------------------- Martin, Could you test against Forge 2.0.0.CR2? Thanks > Creating new project, JVM IBM 1.7 > --------------------------------- > > Key: FORGE-1335 > URL: https://issues.jboss.org/browse/FORGE-1335 > Project: Forge > Issue Type: Bug > Affects Versions: 1.4.3.Final > Environment: JVM: IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 Compressed References 20130205_137358 (JIT enabled, AOT enabled) > OS: Ubuntu 13.04 64 bit > Reporter: Martin Basovnik > Fix For: 2.x Future > > > Problem with creating of new project on JVM ibm17. > LOG: > {noformat} > [no project] test-forge $ new-project --named IBM > ? Use [/home/mbasovni/development/test-forge/IBM] as project directory? [Y/n] > Wrote /home/mbasovni/development/test-forge/IBM > Wrote /home/mbasovni/development/test-forge/IBM/pom.xml > Wrote /home/mbasovni/development/test-forge/IBM/src/main/java > Wrote /home/mbasovni/development/test-forge/IBM/src/test/java > Wrote /home/mbasovni/development/test-forge/IBM/src/main/resources > Wrote /home/mbasovni/development/test-forge/IBM/src/test/resources > ***ERROR*** Exception encountered: null (type "set VERBOSE true" to enable stack traces) > {noformat} > When I set: {{set VERBOSE true}} > LOG: > {noformat} > [no project] test-forge $ set VERBOSE true > [no project] test-forge $ new-project --named IBM2 > ? Use [/home/mbasovni/development/test-forge/IBM2] as project directory? [Y/n] > Wrote /home/mbasovni/development/test-forge/IBM2 > Wrote /home/mbasovni/development/test-forge/IBM2/pom.xml > Wrote /home/mbasovni/development/test-forge/IBM2/src/main/java > Wrote /home/mbasovni/development/test-forge/IBM2/src/test/java > Wrote /home/mbasovni/development/test-forge/IBM2/src/main/resources > Wrote /home/mbasovni/development/test-forge/IBM2/src/test/resources > ***ERROR*** Exception encountered: (type "set VERBOSE false" to disable stack traces) > java.util.NoSuchElementException > at org.sonatype.guice.bean.locators.LocatedBeans$Itr.next(LocatedBeans.java:184) > at org.sonatype.guice.bean.locators.LocatedBeans$Itr.next(LocatedBeans.java:124) > at org.sonatype.guice.plexus.locators.DefaultPlexusBeans$Itr.next(DefaultPlexusBeans.java:64) > at org.sonatype.guice.plexus.locators.DefaultPlexusBeans$Itr.next(DefaultPlexusBeans.java:52) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:243) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:235) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:229) > at org.jboss.forge.maven.facets.MavenContainer.lookup(MavenContainer.java:214) > at org.jboss.forge.maven.facets.MavenContainer.getBuildingRequest(MavenContainer.java:86) > at org.jboss.forge.maven.facets.MavenContainer.getRequest(MavenContainer.java:68) > at org.jboss.forge.maven.facets.MavenContainer$Proxy$_$$_WeldClientProxy.getRequest(MavenContainer$Proxy$_$$_WeldClientProxy.java) > at org.jboss.forge.maven.facets.MavenCoreFacetImpl.getPartialProjectBuildingResult(MavenCoreFacetImpl.java:90) > at org.jboss.forge.maven.facets.MavenCoreFacetImpl.resolveProperties(MavenCoreFacetImpl.java:338) > at org.jboss.forge.maven.facets.MavenDependencyFacet.resolveProperties(MavenDependencyFacet.java:394) > at org.jboss.forge.maven.facets.MavenDependencyFacet.hasEffectiveDependency(MavenDependencyFacet.java:172) > at org.jboss.forge.shell.project.DependencyInstallerImpl.isInstalled(DependencyInstallerImpl.java:170) > at org.jboss.forge.git.GitAPIFacet.isInstalled(GitAPIFacet.java:42) > at org.jboss.forge.project.BaseProject.registerFacet(BaseProject.java:153) > at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:208) > at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:186) > at org.jboss.forge.project.services.ProjectFactory.registerFacets(ProjectFactory.java:178) > at org.jboss.forge.project.services.ProjectFactory.createProject(ProjectFactory.java:146) > at org.jboss.forge.shell.plugins.builtin.NewProjectPlugin.create(NewProjectPlugin.java:205) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:613) > at org.jboss.forge.shell.command.Execution.perform(Execution.java:160) > at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:109) > at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:47) > at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:796) > at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:819) > at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:609) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:613) > at org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48) > at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125) > at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.doShell(ShellImpl$Proxy$_$$_WeldClientProxy.java) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:613) > at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) > at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) > at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) > at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) > at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188) > at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234) > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:622) > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616) > at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:186) > at java.lang.Thread.run(Thread.java:780) > {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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1433) Missing commands in Forge 2.Beta

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1433?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1433. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Final (was: 2.x Future) Resolution: Done > Missing commands in Forge 2.Beta > -------------------------------- > > Key: FORGE-1433 > URL: https://issues.jboss.org/browse/FORGE-1433 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.0.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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1296) Allow constraints to be specified on the versions of the Facets during setup

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1296?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1296: ----------------------------------- Status: Open (was: Pull Request Sent) Git Pull Request: (was: https://github.com/forge/core/pull/358) > Allow constraints to be specified on the versions of the Facets during setup > ---------------------------------------------------------------------------- > > Key: FORGE-1296 > URL: https://issues.jboss.org/browse/FORGE-1296 > Project: Forge > Issue Type: Feature Request > Components: UI - API > Affects Versions: 2.0.0.Alpha14 > Reporter: Vineet Reynolds > Assignee: George Gastaldi > Fix For: 2.x Future > > > The current implementation of the Scaffold and possibly other addons, verifies if facets are setup and then proceeds to add the wizards for these facets to the NavigationResult. > It is possible that some of the versions displayed in the individual wizards will not be applicable when used in a composite wizard like the scaffold. We need to find a way for the composite to hint or specify the allowed versions of the individual facets. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1296) Allow constraints to be specified on the versions of the Facets during setup

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1296?page=com.atlassian.jira.plugin... ] George Gastaldi reassigned FORGE-1296: -------------------------------------- Assignee: (was: George Gastaldi) > Allow constraints to be specified on the versions of the Facets during setup > ---------------------------------------------------------------------------- > > Key: FORGE-1296 > URL: https://issues.jboss.org/browse/FORGE-1296 > Project: Forge > Issue Type: Feature Request > Components: UI - API > Affects Versions: 2.0.0.Alpha14 > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > The current implementation of the Scaffold and possibly other addons, verifies if facets are setup and then proceeds to add the wizards for these facets to the NavigationResult. > It is possible that some of the versions displayed in the individual wizards will not be applicable when used in a composite wizard like the scaffold. We need to find a way for the composite to hint or specify the allowed versions of the individual facets. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1384) forge2: add description text & example panels to "Forge Run Command" dialog

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1384?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1384: ----------------------------------- Priority: Major (was: Blocker) > forge2: add description text & example panels to "Forge Run Command" dialog > --------------------------------------------------------------------------- > > Key: FORGE-1384 > URL: https://issues.jboss.org/browse/FORGE-1384 > Project: Forge > Issue Type: Feature Request > Components: UI - Eclipse > Affects Versions: 2.0.0.Beta3 > Environment: Linux > Reporter: Gavin Flower > Assignee: Koen Aers > Fix For: 2.x Future > > > There is currently a tooltip, but it does not add really add much to what could be gained from the command name! > It might be a good idea to have a variable sized scrollable text panel in the bottom half to give a more detailed explanation. As a suitable explanation might range from a single sentence to several paragraphs (in the later case, the first para should be short summary that might be enough to more experienced people). It is important to explain why & when you would want to use the command, as well as what it does. Probably a good idea to say what files it creates and/or modifies... > Plus a second panel for examples, the examples may be in a tree structure, when there is more than one available. Each example would have: > (1) short descriptive name > (2) brief description of what it sets out to achieve and how > (3) the example code itself, along with appropriate comments > An unexpanded leaf will have (1) & as much of (2) as can fit on the rest of the line. When a leaf is expanded then the full detail will be available. In rare cases you might need several levels to group related examples together. > The target audience will consist of people who are totally new to Forge and to JEE, to those people with considerable related experience, as well as experienced developers from other areas (For example I started with FORTRAN & COBOL over 40 years ago, and have been doing Java for over 10 years, but relatively inexperienced in JEE). -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1485) Rename --target for faces-new-validator-method command

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1485?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1485. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Final (was: 2.x Future) Resolution: Done > Rename --target for faces-new-validator-method command > ------------------------------------------------------- > > Key: FORGE-1485 > URL: https://issues.jboss.org/browse/FORGE-1485 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.0.0.Final > > > The {{faces-new-validator-method}} has a {{--target}} parameter but without TAB completion, we don't know what this actually targets. When we hit TAB we get : > {code} > [Language.java]$ faces-new-validator-method --target > Author.java Item.java Language.java Publisher.java > {code} > Most of the {{target}} parameters are suffixed to be more explicit : > {code} > entities-from-tables --targetPackage > faces-new-converter --targetPackage > project-new --targetLocation > {code} > So I would rename it {{targetClass}} : > {code} > faces-new-validator-method --targetClass > {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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1517) EJBs shouldn't be created under the model subpackage

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1517?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1517. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Final (was: 2.x Future) Resolution: Done > EJBs shouldn't be created under the model subpackage > ---------------------------------------------------- > > Key: FORGE-1517 > URL: https://issues.jboss.org/browse/FORGE-1517 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.0.0.Final > > > By default EJBs are created under the {{model}} subpackage : > {code} > [pluralsight-persistence]$ ejb-new-bean --named MyEJBService > ***SUCCESS*** EJB com.pluralsight.persistence.module07.model.MyEJBService created. > {code} > I can't remember what was the behaviour un Forge 1.x. But model is for JPA entities. Maybe {{service}} should be a better name. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1518) --packageName on rest-setup should be renamed to --targetPackage

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1518?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1518. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Final (was: 2.x Future) Resolution: Done > --packageName on rest-setup should be renamed to --targetPackage > ---------------------------------------------------------------- > > Key: FORGE-1518 > URL: https://issues.jboss.org/browse/FORGE-1518 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.0.0.Final > > > {{packageName}} should be renamed {{targetPackage}}. So instead of : > {code} > [Test]$ rest-setup > --jaxrsVersion --applicationPath --config --packageName --className > {code} > {code} > [Test]$ rest-setup > --jaxrsVersion --applicationPath --config --targetPackage --className > {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

12 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues January 2014