May 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-861) Forge 2 does not start upon installation into Eclipse. Must restart eclipse.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-861?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-861: ---------------------------------- Fix Version/s: 2.0.0.Alpha5 (was: 2.0.0.Alpha4) > Forge 2 does not start upon installation into Eclipse. Must restart eclipse. > ---------------------------------------------------------------------------- > > Key: FORGE-861 > URL: https://issues.jboss.org/browse/FORGE-861 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Affects Versions: 2.0.0.Alpha2 > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha5 > > > Technically this issue is in the JBDS side, but since it is related to Forge 2 only, I put the issue here for now. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-898) "Install an Addon" command should allow quick-selection of "org.jboss.forge" core addons.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-898?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-898: ---------------------------------- Fix Version/s: 2.0.0.Alpha5 (was: 2.0.0.Alpha4) > "Install an Addon" command should allow quick-selection of "org.jboss.forge" core addons. > ----------------------------------------------------------------------------------------- > > Key: FORGE-898 > URL: https://issues.jboss.org/browse/FORGE-898 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins, Usability > Affects Versions: 2.0.0.Alpha3 > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha5 > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-896) Different Facets for main and test sources/resources

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-896?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-896: ---------------------------------- Fix Version/s: 2.0.0.Alpha5 (was: 2.0.0.Alpha4) > Different Facets for main and test sources/resources > ---------------------------------------------------- > > Key: FORGE-896 > URL: https://issues.jboss.org/browse/FORGE-896 > Project: Forge > Issue Type: Enhancement > Components: Maven Integration > Affects Versions: 2.0.0.Alpha3 > Reporter: George Gastaldi > Fix For: 2.0.0.Alpha5 > > > It should be possible to have a facet to create the src/main/* structure and another facet for src/test/*. > JavaSourceFacet and ResourceFacet should be split into two different interfaces to allow that -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-903) RestFacet is not properly installed

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-903?page=com.atlassian.jira.plugin.... ] Vineet Reynolds closed FORGE-903. --------------------------------- Resolution: Done Pushed upstream https://github.com/forge/core/commit/b2e6069f1102d23a96fdfc38479be6deb529... > RestFacet is not properly installed > ----------------------------------- > > Key: FORGE-903 > URL: https://issues.jboss.org/browse/FORGE-903 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins, Java EE APIs > Affects Versions: 1.2.3.Final > Reporter: George Gastaldi > Assignee: Vineet Reynolds > Fix For: 1.3.0.Final > > > When a plugin X depends on RestFacet, it is assumed that when the plugin X is run, REST should be already configured. > This is not happening since the configuration steps lies inside the RestPlugin class, executing only the addition of the REST dependencies in the project's pom.xml. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-710) Forge shell hangs on exit

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/FORGE-710?page=com.atlassian.jira.plugin.... ] James Perkins commented on FORGE-710: ------------------------------------- That very well could be. While I still need to review it and push it upstream, I did remove the console redirect on a PR I have open. > Forge shell hangs on exit > ------------------------- > > Key: FORGE-710 > URL: https://issues.jboss.org/browse/FORGE-710 > Project: Forge > Issue Type: Bug > Components: UI - Shell > Affects Versions: 1.1.2.Final > Environment: Fedora 17 Linux 3.6.7-4.fc17.x86_64 #1 SMP Tue Nov 20 19:40:01 UTC 2012 x86_64 x86_64 GNU/Linux > java version "1.6.0_37" > Java(TM) SE Runtime Environment (build 1.6.0_37-b06) > Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01, mixed mode) > Reporter: James Perkins > Assignee: James Perkins > Attachments: jstacktrace, kill-3 > > > When attempting to exit Forge by typing exit and pressing enter a hang occurs. Using CTRL+D does seem to work. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-903) RestFacet is not properly installed

by George Gastaldi (JIRA)

George Gastaldi created FORGE-903: ------------------------------------- Summary: RestFacet is not properly installed Key: FORGE-903 URL: https://issues.jboss.org/browse/FORGE-903 Project: Forge Issue Type: Bug Components: Builtin Plugins, Java EE APIs Affects Versions: 1.2.3.Final Reporter: George Gastaldi Assignee: Vineet Reynolds Fix For: 1.3.0.Final When a plugin X depends on RestFacet, it is assumed that when the plugin X is run, REST should be already configured. This is not happening since the configuration steps lies inside the RestPlugin class, executing only the addition of the REST dependencies in the project's pom.xml. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-902) RmPlugin should not prompt for non-existing resources

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-902?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-902. --------------------------------- Resolution: Done > RmPlugin should not prompt for non-existing resources > ----------------------------------------------------- > > Key: FORGE-902 > URL: https://issues.jboss.org/browse/FORGE-902 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 1.2.3.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 1.3.0.Final > > > The RmPlugin prompts when trying to remove a resource that doesn't exist. > It should show an error message when rm is invoked in a non-existing resource -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-902) RmPlugin should not prompt for non-existing resources

by George Gastaldi (JIRA)

George Gastaldi created FORGE-902: ------------------------------------- Summary: RmPlugin should not prompt for non-existing resources Key: FORGE-902 URL: https://issues.jboss.org/browse/FORGE-902 Project: Forge Issue Type: Bug Components: Builtin Plugins Affects Versions: 1.2.3.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 1.3.0.Final The RmPlugin prompts when trying to remove a resource that doesn't exist. It should show an error message when rm is invoked in a non-existing resource -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-901) Error while running persistence setup when current persistence.xml is deleted

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-901?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-901. --------------------------------- Resolution: Done > Error while running persistence setup when current persistence.xml is deleted > ----------------------------------------------------------------------------- > > Key: FORGE-901 > URL: https://issues.jboss.org/browse/FORGE-901 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 1.2.3.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 1.3.0.Final > > > {code} > [myjsapp] myjsapp $ rm src/main/resources/META-INF/persistence.xml > ? delete: persistence.xml: are you sure? [Y/n] > Deleted /Downloads/workspace/myjsapp/src/main/resources/META-INF/persistence.xml > [myjsapp] myjsapp $ persistence setup --provider HIBERNATE --container JBOSS_AS7 > org.jboss.forge.resources.ResourceException: cannot obtain stream to file: file does not exist: /Downloads/workspace/myjsapp/src/main/resources/META-INF/persistence.xml > ***ERROR*** Exception encountered: (type "set VERBOSE false" to disable stack traces) > at org.jboss.forge.resources.FileResource.getResourceInputStream(FileResource.java:91) > at org.jboss.forge.spec.javaee.jpa.PersistenceFacetImpl.getConfig(PersistenceFacetImpl.java:115) > at org.jboss.forge.spec.javaee.jpa.PersistencePlugin.setup(PersistencePlugin.java:156) > 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:601) > at org.jboss.forge.shell.command.Execution.perform(Execution.java:155) > 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:795) > at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:818) > at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:608) > 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:601) > 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:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > 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:722) > {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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-901) Error while running persistence setup when current persistence.xml is deleted

by George Gastaldi (JIRA)

George Gastaldi created FORGE-901: ------------------------------------- Summary: Error while running persistence setup when current persistence.xml is deleted Key: FORGE-901 URL: https://issues.jboss.org/browse/FORGE-901 Project: Forge Issue Type: Bug Components: Builtin Plugins Affects Versions: 1.2.3.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 1.3.0.Final {code} [myjsapp] myjsapp $ rm src/main/resources/META-INF/persistence.xml ? delete: persistence.xml: are you sure? [Y/n] Deleted /Downloads/workspace/myjsapp/src/main/resources/META-INF/persistence.xml [myjsapp] myjsapp $ persistence setup --provider HIBERNATE --container JBOSS_AS7 org.jboss.forge.resources.ResourceException: cannot obtain stream to file: file does not exist: /Downloads/workspace/myjsapp/src/main/resources/META-INF/persistence.xml ***ERROR*** Exception encountered: (type "set VERBOSE false" to disable stack traces) at org.jboss.forge.resources.FileResource.getResourceInputStream(FileResource.java:91) at org.jboss.forge.spec.javaee.jpa.PersistenceFacetImpl.getConfig(PersistenceFacetImpl.java:115) at org.jboss.forge.spec.javaee.jpa.PersistencePlugin.setup(PersistencePlugin.java:156) 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:601) at org.jboss.forge.shell.command.Execution.perform(Execution.java:155) 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:795) at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:818) at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:608) 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:601) 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:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) 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:722) {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, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues May 2013