October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13156) Cannot install jboss-as-7 plugin

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13156?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-13156. ------------------------------- Resolution: Won't Fix > Cannot install jboss-as-7 plugin > -------------------------------- > > Key: JBIDE-13156 > URL: https://issues.jboss.org/browse/JBIDE-13156 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.0.0.CR1 > Environment: jbdevstudio-6.0.0.CR1a build > Reporter: Pavol Srna > Assignee: Koen Aers > Priority: Minor > > I'm unable to install jboss-as-7 plugin. Embedded forge runtime was updated to Forge.1.1.2.Final (https://issues.jboss.org/browse/JBIDE-13108) but I still cannot install jboss-as-7 plugin from within the tooling. I tried in forge runtime 1.1.2.Final and there are no problems, so it looks like tooling issue. > StackTrace: > ----------- > {code} > at org.jboss.forge.maven.facets.MavenProjectBuilder.build(MavenProjectBuilder.java:86) > at org.jboss.forge.shell.plugins.builtin.ForgePlugin.buildFromCurrentProject(ForgePlugin.java:633) > at org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromGit(ForgePlugin.java:404) > at org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromIndex(ForgePlugin.java:245) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.forge.shell.command.Execution.perform(Execution.java:134) > 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:818) > at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:841) > at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:631) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > 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:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > 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:172) > at java.lang.Thread.run(Thread.java:662) > {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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13156) Cannot install jboss-as-7 plugin

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13156?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-13156: ----------------------------------- With the Forge 2 integration around the corner and because the phasing out of the Forge 1 integration is near, I will resolve this bug as "Won't Fix" > Cannot install jboss-as-7 plugin > -------------------------------- > > Key: JBIDE-13156 > URL: https://issues.jboss.org/browse/JBIDE-13156 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.0.0.CR1 > Environment: jbdevstudio-6.0.0.CR1a build > Reporter: Pavol Srna > Assignee: Koen Aers > Priority: Minor > > I'm unable to install jboss-as-7 plugin. Embedded forge runtime was updated to Forge.1.1.2.Final (https://issues.jboss.org/browse/JBIDE-13108) but I still cannot install jboss-as-7 plugin from within the tooling. I tried in forge runtime 1.1.2.Final and there are no problems, so it looks like tooling issue. > StackTrace: > ----------- > {code} > at org.jboss.forge.maven.facets.MavenProjectBuilder.build(MavenProjectBuilder.java:86) > at org.jboss.forge.shell.plugins.builtin.ForgePlugin.buildFromCurrentProject(ForgePlugin.java:633) > at org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromGit(ForgePlugin.java:404) > at org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromIndex(ForgePlugin.java:245) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.forge.shell.command.Execution.perform(Execution.java:134) > 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:818) > at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:841) > at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:631) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > 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:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > 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:172) > at java.lang.Thread.run(Thread.java:662) > {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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12103) Forge Console stopps working

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12103?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-12103: ------------------------------ Fix Version/s: (was: 3.3.x) (was: 4.0.x) > Forge Console stopps working > ---------------------------- > > Key: JBIDE-12103 > URL: https://issues.jboss.org/browse/JBIDE-12103 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 3.3.0.CR1, 3.3.0.Final > Reporter: Juergen Zimmermann > Assignee: Koen Aers > Attachments: forge-console.pdf > > > I tried JBoss Tools 3.3.0.CR1 2012-06-04_21-27-23-H174: the Forge Console stopps working. Please see also https://issues.jboss.org/browse/FORGE-591. I'll attach a screenshot. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12103) Forge Console stopps working

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12103?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-12103: ----------------------------------- This issue is out of date. If you can still reproduce it, feel free to reopen with detailed information on how to do this. > Forge Console stopps working > ---------------------------- > > Key: JBIDE-12103 > URL: https://issues.jboss.org/browse/JBIDE-12103 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 3.3.0.CR1, 3.3.0.Final > Reporter: Juergen Zimmermann > Assignee: Koen Aers > Attachments: forge-console.pdf > > > I tried JBoss Tools 3.3.0.CR1 2012-06-04_21-27-23-H174: the Forge Console stopps working. Please see also https://issues.jboss.org/browse/FORGE-591. I'll attach a screenshot. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12103) Forge Console stopps working

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12103?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-12103. ------------------------------- Resolution: Out of Date > Forge Console stopps working > ---------------------------- > > Key: JBIDE-12103 > URL: https://issues.jboss.org/browse/JBIDE-12103 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 3.3.0.CR1, 3.3.0.Final > Reporter: Juergen Zimmermann > Assignee: Koen Aers > Attachments: forge-console.pdf > > > I tried JBoss Tools 3.3.0.CR1 2012-06-04_21-27-23-H174: the Forge Console stopps working. Please see also https://issues.jboss.org/browse/FORGE-591. I'll attach a screenshot. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12743) Forge tools should add new projects created with forge to the current working set(s)

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12743?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-12743: ------------------------------ Fix Version/s: 4.2.x (was: 4.0.x) (was: 4.1.x) > Forge tools should add new projects created with forge to the current working set(s) > ------------------------------------------------------------------------------------ > > Key: JBIDE-12743 > URL: https://issues.jboss.org/browse/JBIDE-12743 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 4.0.0.Alpha1 > Reporter: Lincoln Baxter III > Assignee: Koen Aers > Priority: Minor > Fix For: 4.2.x > > > It would be nice if new projects created with forge were added to the current working set automatically (or prompted for one,) so that it doesn't look like the project is "missing" upon creation when working in a working set. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12743) Forge tools should add new projects created with forge to the current working set(s)

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12743?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-12743: ----------------------------------- This should probably not be done anymore for the Forge 1 integration. But it's definitely an idea to keep for the Forge 2 integration. > Forge tools should add new projects created with forge to the current working set(s) > ------------------------------------------------------------------------------------ > > Key: JBIDE-12743 > URL: https://issues.jboss.org/browse/JBIDE-12743 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 4.0.0.Alpha1 > Reporter: Lincoln Baxter III > Assignee: Koen Aers > Priority: Minor > Fix For: 4.2.x > > > It would be nice if new projects created with forge were added to the current working set automatically (or prompted for one,) so that it doesn't look like the project is "missing" upon creation when working in a working set. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13180) Improve Error Handling When Specifying VM Arguments For Forge

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13180?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-13180: ----------------------------------- With Forge 2 around the corner and the start of phasing out the Forge 1 integration near, this bug will not be fixed. > Improve Error Handling When Specifying VM Arguments For Forge > ------------------------------------------------------------- > > Key: JBIDE-13180 > URL: https://issues.jboss.org/browse/JBIDE-13180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.0.0.Final > Reporter: Koen Aers > Assignee: Koen Aers > > When specifying erroneously arguments like "-Xmx=512m" the VM halts. The error message is not properly forwarded to the user leaving him in doubt as to what has happened. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13180) Improve Error Handling When Specifying VM Arguments For Forge

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13180?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-13180. ------------------------------- Resolution: Won't Fix > Improve Error Handling When Specifying VM Arguments For Forge > ------------------------------------------------------------- > > Key: JBIDE-13180 > URL: https://issues.jboss.org/browse/JBIDE-13180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.0.0.Final > Reporter: Koen Aers > Assignee: Koen Aers > > When specifying erroneously arguments like "-Xmx=512m" the VM halts. The error message is not properly forwarded to the user leaving him in doubt as to what has happened. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13180) Improve Error Handling When Specifying VM Arguments For Forge

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13180?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-13180: ------------------------------ Fix Version/s: (was: 4.0.x) (was: 4.1.x) > Improve Error Handling When Specifying VM Arguments For Forge > ------------------------------------------------------------- > > Key: JBIDE-13180 > URL: https://issues.jboss.org/browse/JBIDE-13180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.0.0.Final > Reporter: Koen Aers > Assignee: Koen Aers > > When specifying erroneously arguments like "-Xmx=512m" the VM halts. The error message is not properly forwarded to the user leaving him in doubt as to what has happened. -- 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, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2013