[JBoss JIRA] (FORGE-1056) Create a Guice Furnace container
by George Gastaldi (JIRA)
George Gastaldi created FORGE-1056:
--------------------------------------
Summary: Create a Guice Furnace container
Key: FORGE-1056
URL: https://issues.jboss.org/browse/FORGE-1056
Project: Forge
Issue Type: Feature Request
Components: Furnace (Container)
Affects Versions: 2.0.0.Alpha8
Reporter: George Gastaldi
Fix For: 2.x Future
It would be interesting to have a Spring addon to demonstrate that Furnace is "dependency injection agnostic". It would be nice to envolve the Snowdrop Team on this task
--
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, 9 months
[JBoss JIRA] (FORGE-1043) Unable to install AS7 plugin
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1043?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III closed FORGE-1043.
-------------------------------------
Assignee: Lincoln Baxter III
Resolution: Out of Date
Thanks for responding! Glad it works for you now! Sorry you had trouble at first, that's never good :(
> Unable to install AS7 plugin
> -----------------------------
>
> Key: FORGE-1043
> URL: https://issues.jboss.org/browse/FORGE-1043
> Project: Forge
> Issue Type: Feature Request
> Affects Versions: 1.3.3.Final
> Environment: JBoss Forge, version [ 1.1.1.Final ] - JBoss, by Red Hat, Inc. [ http://jboss.org/forge ]
> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Maven home: /opt/java/maven
> Java version: 1.7.0_10-ea, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_10.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.8.4", arch: "x86_64", family: "mac"
> Reporter: Hardy Ferentschik
> Assignee: Lincoln Baxter III
>
> Trying to follow the forge-from-scratch (http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/forge-from-scratch/) tutorial, I reached the point where I am supposed to install the AS 7 plugin. I get (verbose format):
> {noformat}
> [demo] demo $ forge install-plugin jboss-as-7
> Connecting to remote repository [https://raw.github.com/forge/plugin-repository/master/repository.yaml]... connected!
> ***INFO*** Preparing to install plugin: jboss-as-7
> ***INFO*** Checking out plugin source files to [/var/folders/0p/_bb9yrwj0xvb1f_98jp8h_c40000gn/T/forgetemp3225640766693782497/repo] via 'git'
> ***INFO*** Switching to branch/tag [refs/tags/1.0.5.Final]
> ? The project does not appear to be a Forge Plugin Project, install anyway? [y/N] y
> Wrote /Users/hardy/.forge/httpsrawgithubcomforgepluginrepositorymasterrepositoryyaml.yaml
> ***ERROR*** Exception encountered: (type "set VERBOSE false" to disable stack traces)
> java.lang.NullPointerException
> at org.jboss.forge.shell.plugins.builtin.ForgePlugin.buildFromCurrentProject(ForgePlugin.java:616)
> at org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromGit(ForgePlugin.java:398)
> at org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromIndex(ForgePlugin.java:239)
> 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: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: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:172)
> at java.lang.Thread.run(Thread.java:722)
> {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
10 years, 9 months
[JBoss JIRA] (FORGE-1034) Upgrade forge-maven-plugin to use furnace-manager
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/FORGE-1034?page=com.atlassian.jira.plugin... ]
Mickael Istria commented on FORGE-1034:
---------------------------------------
> The forge-maven-plugin retrieves the required addons in order to make Forge 2 usable in Eclipse and copy them to an addon-repository folder that is created during build time.
Can you please provide a link to the place in jbosstools-forge repository where this plugin is used? I had a quick look at som pom files and didn't find a reference to this plugin
[~maxandersen]: With the move to Tycho 0.18.1, JBT build supports both Maven 3.0.x and Maven 3.1.0. The only benefit so far is that is makes developers' life easier (they won't have to deal with multiple versions of Maven and can use the one of their choice to build JBT). Moving to Tycho 0.18.1 is a way to let [~gastaldi] and friends keep only a single version of Maven to build both JBT and forge-maven-plugin.
> Upgrade forge-maven-plugin to use furnace-manager
> -------------------------------------------------
>
> Key: FORGE-1034
> URL: https://issues.jboss.org/browse/FORGE-1034
> Project: Forge
> Issue Type: Component Upgrade
> Components: Maven Plugin
> Affects Versions: 2.0.0.Alpha6
> Reporter: George Gastaldi
> Assignee: 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
10 years, 9 months
[JBoss JIRA] (FORGE-1034) Upgrade forge-maven-plugin to use furnace-manager
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1034?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-1034:
----------------------------------------
As replied in the e-mail:
{quote}
>
> why is the forge-maven-plugin relevant for the eclipse plugins build ?
The forge-maven-plugin retrieves the required addons in order to make Forge 2 usable in Eclipse and copy them to an addon-repository folder that is created during build time. This is to prevent binaries being pushed to the forge git repository. There is an older version of the plugin already doing this but for some strange reason behind the classworld land, Aether 1.13.1 (used to fetch the declared addons) does not work inside a maven plugin targeted for 3.0.5.
> And isn't requiring Mvn 3.1 in Forge 2 going to break other plugins ?
I tested and the build works with Maven 3.1 AFTER Mickael upgraded the tycho plugin version. So that is not an issue afaik.
> afaics the mvn 3.1 release is getting many reports about incompatibilities...
>
> how does that affect our JBDS 7.0/7.1 where mvn 3.0 still needs to work too ?
That should probably require some additional testing. I tested the JBT Forge build and the only plugin that was preventing this to happen was the tycho I as beforementioned, which is now fixed.
{quote}
> Upgrade forge-maven-plugin to use furnace-manager
> -------------------------------------------------
>
> Key: FORGE-1034
> URL: https://issues.jboss.org/browse/FORGE-1034
> Project: Forge
> Issue Type: Component Upgrade
> Components: Maven Plugin
> Affects Versions: 2.0.0.Alpha6
> Reporter: George Gastaldi
> Assignee: 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
10 years, 9 months
[JBoss JIRA] (FORGE-1043) Unable to install AS7 plugin
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/FORGE-1043?page=com.atlassian.jira.plugin... ]
Hardy Ferentschik commented on FORGE-1043:
------------------------------------------
With 1.3.3.Final the plugin installs successfully.
> Unable to install AS7 plugin
> -----------------------------
>
> Key: FORGE-1043
> URL: https://issues.jboss.org/browse/FORGE-1043
> Project: Forge
> Issue Type: Feature Request
> Affects Versions: 1.3.3.Final
> Environment: JBoss Forge, version [ 1.1.1.Final ] - JBoss, by Red Hat, Inc. [ http://jboss.org/forge ]
> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Maven home: /opt/java/maven
> Java version: 1.7.0_10-ea, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_10.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.8.4", arch: "x86_64", family: "mac"
> Reporter: Hardy Ferentschik
>
> Trying to follow the forge-from-scratch (http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/forge-from-scratch/) tutorial, I reached the point where I am supposed to install the AS 7 plugin. I get (verbose format):
> {noformat}
> [demo] demo $ forge install-plugin jboss-as-7
> Connecting to remote repository [https://raw.github.com/forge/plugin-repository/master/repository.yaml]... connected!
> ***INFO*** Preparing to install plugin: jboss-as-7
> ***INFO*** Checking out plugin source files to [/var/folders/0p/_bb9yrwj0xvb1f_98jp8h_c40000gn/T/forgetemp3225640766693782497/repo] via 'git'
> ***INFO*** Switching to branch/tag [refs/tags/1.0.5.Final]
> ? The project does not appear to be a Forge Plugin Project, install anyway? [y/N] y
> Wrote /Users/hardy/.forge/httpsrawgithubcomforgepluginrepositorymasterrepositoryyaml.yaml
> ***ERROR*** Exception encountered: (type "set VERBOSE false" to disable stack traces)
> java.lang.NullPointerException
> at org.jboss.forge.shell.plugins.builtin.ForgePlugin.buildFromCurrentProject(ForgePlugin.java:616)
> at org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromGit(ForgePlugin.java:398)
> at org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromIndex(ForgePlugin.java:239)
> 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: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: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:172)
> at java.lang.Thread.run(Thread.java:722)
> {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
10 years, 9 months
[JBoss JIRA] (FORGE-1054) Forge OpenShift plugin hangs when creating a JBoss app in Windows
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGE-1054?page=com.atlassian.jira.plugin... ]
Vineet Reynolds updated FORGE-1054:
-----------------------------------
Summary: Forge OpenShift plugin hangs when creating a JBoss app in Windows (was: Process wil hang there when creating a jboss app in the window7)
> Forge OpenShift plugin hangs when creating a JBoss app in Windows
> -----------------------------------------------------------------
>
> Key: FORGE-1054
> URL: https://issues.jboss.org/browse/FORGE-1054
> Project: Forge
> Issue Type: Bug
> Affects Versions: 1.3.3.Final
> Environment: Window7
> Git-1.8.3-preview2013.6.1 jdk-7u25-windows-x64
> Reporter: nan wei
>
> Description of problem:
> When creating a jboss app, app creation process hang there.
> Version:
> forge-distribution-1.3.3.Final.zip
> Window7
> Git-1.8.3-preview2013.6.1 jdk-7u25-windows-x64
> How reproducible:
> always
> Steps to Reproduce:
> 1. Ensure that you have already installed a Java 6+ JDK.
> 1.1 install jdk-7u25-windows-x64
> 1.2 set JAVA_HOME.
> 2. Download Forge 1.3.2.Final and Un-zip Forge into a folder on your hard-disk, this folder will be your FORGE_HOME.
> 2.1 Add '$FORGE_HOME/bin' to your windows path.
> 2.2 installing Git(Git-1.8.3-preview2013.6.1)
> 3. Open a command prompt and run 'forge.bat'.
> 4. Install OpenShift plugin for forge.
> 5. create a jboss app.
> Actual results:
> [forge-openshift-demo] forge-openshift-demo $ rhc setup
> ***INFO*** Loaded OpenShift configuration from C:\Users\nanwei/.openshift/expres
> s.conf
> ? Enter the application name [forgeopenshiftd] [forgeopenshiftd] wsy
> ***INFO*** Using RHLOGIN:nwei for https://10.4.59.171
> ? Enter your Red Hat Openshift password: ******
> ***INFO*** Found OpenShift User: nwei
> Choose a JBoss Cartridge:
>
> 1 - [Cartridge [name=jbosseap-6.0]]*
> 2 - [Cartridge [name=jbossews-2.0]]
> 3 - [Cartridge [name=jbossews-1.0]]
>
> ? Choose an option by typing the number of the selection [*-default] [0] 1
> ***INFO*** Using JBoss Cartridge: jbosseap-6.0
> Initialized empty Git repository in C:/Users/nanwei/Downloads/forge/bin/forge-op
> enshift-demo/.git/
> ***INFO*** Waiting for OpenShift to propagate DNS
> ***INFO*** Trying to contact http://forge-nweidomain.osetestv2.com/ (attempt 1 of
> 500)
> Updating openshift
> Expected results:
> The process will hang there for ever.
> Additional info:
--
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, 9 months
[JBoss JIRA] (FORGE-1055) Process wil hang there when creating a jboss app in the window7
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGE-1055?page=com.atlassian.jira.plugin... ]
Vineet Reynolds closed FORGE-1055.
----------------------------------
Resolution: Duplicate Issue
Duplicate of FORGE-1054.
> Process wil hang there when creating a jboss app in the window7
> ---------------------------------------------------------------
>
> Key: FORGE-1055
> URL: https://issues.jboss.org/browse/FORGE-1055
> Project: Forge
> Issue Type: Bug
> Affects Versions: 1.3.3.Final
> Environment: Window7
> Git-1.8.3-preview2013.6.1 jdk-7u25-windows-x64
> Reporter: nan wei
>
> Description of problem:
> When creating a jboss app, app creation process hang there.
> Version:
> forge-distribution-1.3.3.Final.zip
> Window7
> Git-1.8.3-preview2013.6.1 jdk-7u25-windows-x64
> How reproducible:
> always
> Steps to Reproduce:
> 1. Ensure that you have already installed a Java 6+ JDK.
> 1.1 install jdk-7u25-windows-x64
> 1.2 set JAVA_HOME.
> 2. Download Forge 1.3.2.Final and Un-zip Forge into a folder on your hard-disk, this folder will be your FORGE_HOME.
> 2.1 Add '$FORGE_HOME/bin' to your windows path.
> 2.2 installing Git(Git-1.8.3-preview2013.6.1)
> 3. Open a command prompt and run 'forge.bat'.
> 4. Install OpenShift plugin for forge.
> 5. create a jboss app.
> Actual results:
> [forge-openshift-demo] forge-openshift-demo $ rhc setup
> ***INFO*** Loaded OpenShift configuration from C:\Users\nanwei/.openshift/expres
> s.conf
> ? Enter the application name [forgeopenshiftd] [forgeopenshiftd] wsy
> ***INFO*** Using RHLOGIN:nwei for https://10.4.59.171
> ? Enter your Red Hat Openshift password: ******
> ***INFO*** Found OpenShift User: nwei
> Choose a JBoss Cartridge:
>
> 1 - [Cartridge [name=jbosseap-6.0]]*
> 2 - [Cartridge [name=jbossews-2.0]]
> 3 - [Cartridge [name=jbossews-1.0]]
>
> ? Choose an option by typing the number of the selection [*-default] [0] 1
> ***INFO*** Using JBoss Cartridge: jbosseap-6.0
> Initialized empty Git repository in C:/Users/nanwei/Downloads/forge/bin/forge-op
> enshift-demo/.git/
> ***INFO*** Waiting for OpenShift to propagate DNS
> ***INFO*** Trying to contact http://forge-nweidomain.osetestv2.com/ (attempt 1 of
> 500)
> Updating openshift
> Expected results:
> The process will hang there for ever.
> Additional info:
--
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, 9 months