July 2013 - forge-issues - Jboss List Archives

[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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1055) Process wil hang there when creating a jboss app in the window7

by nan wei (JIRA)

[ https://issues.jboss.org/browse/FORGE-1055?page=com.atlassian.jira.plugin... ] nan wei closed FORGE-1055. -------------------------- Resolution: Done > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1055) Process wil hang there when creating a jboss app in the window7

by nan wei (JIRA)

nan wei created FORGE-1055: ------------------------------ Summary: 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1054) Process wil hang there when creating a jboss app in the window7

by nan wei (JIRA)

nan wei created FORGE-1054: ------------------------------ Summary: Process wil hang there when creating a jboss app in the window7 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, 10 months

1
0
0 / 0

[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: ---------------------------------------- Build with Maven 3.1.0 now works with JBT having 4.2.0.Alpha1-SNAPSHOT as parent. > 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, 10 months

1
0
0 / 0

[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: ---------------------------------------- If you try to run the build with Maven 3.1.0, the following error happens: {code} [INFO] Scanning for projects... --------------------------------------------------- constituent[0]: file:/opt/apache-maven-3.1.0/lib/asm-3.3.1.jar constituent[1]: file:/opt/apache-maven-3.1.0/lib/javax.inject-1.jar constituent[2]: file:/opt/apache-maven-3.1.0/lib/cdi-api-1.0.jar constituent[3]: file:/opt/apache-maven-3.1.0/lib/plexus-cipher-1.7.jar constituent[4]: file:/opt/apache-maven-3.1.0/lib/maven-compat-3.1.0.jar constituent[5]: file:/opt/apache-maven-3.1.0/lib/maven-embedder-3.1.0.jar constituent[6]: file:/opt/apache-maven-3.1.0/lib/maven-aether-provider-3.1.0.jar constituent[7]: file:/opt/apache-maven-3.1.0/lib/sisu-guice-3.1.3-no_aop.jar constituent[8]: file:/opt/apache-maven-3.1.0/lib/wagon-provider-api-2.4.jar constituent[9]: file:/opt/apache-maven-3.1.0/lib/maven-model-3.1.0.jar constituent[10]: file:/opt/apache-maven-3.1.0/lib/commons-cli-1.2.jar constituent[11]: file:/opt/apache-maven-3.1.0/lib/aether-util-0.9.0.M2.jar constituent[12]: file:/opt/apache-maven-3.1.0/lib/org.eclipse.sisu.plexus-0.0.0.M2a.jar constituent[13]: file:/opt/apache-maven-3.1.0/lib/guava-11.0.2.jar constituent[14]: file:/opt/apache-maven-3.1.0/lib/aopalliance-1.0.jar constituent[15]: file:/opt/apache-maven-3.1.0/lib/org.eclipse.sisu.inject-0.0.0.M2a.jar constituent[16]: file:/opt/apache-maven-3.1.0/lib/slf4j-simple-1.7.4.jar constituent[17]: file:/opt/apache-maven-3.1.0/lib/maven-artifact-3.1.0.jar constituent[18]: file:/opt/apache-maven-3.1.0/lib/maven-repository-metadata-3.1.0.jar constituent[19]: file:/opt/apache-maven-3.1.0/lib/aether-api-0.9.0.M2.jar constituent[20]: file:/opt/apache-maven-3.1.0/lib/aether-impl-0.9.0.M2.jar constituent[21]: file:/opt/apache-maven-3.1.0/lib/maven-plugin-api-3.1.0.jar constituent[22]: file:/opt/apache-maven-3.1.0/lib/plexus-interpolation-1.16.jar constituent[23]: file:/opt/apache-maven-3.1.0/lib/maven-settings-3.1.0.jar constituent[24]: file:/opt/apache-maven-3.1.0/lib/aether-spi-0.9.0.M2.jar constituent[25]: file:/opt/apache-maven-3.1.0/lib/plexus-component-annotations-1.5.5.jar constituent[26]: file:/opt/apache-maven-3.1.0/lib/wagon-file-2.4.jar constituent[27]: file:/opt/apache-maven-3.1.0/lib/wagon-http-2.4-shaded.jar constituent[28]: file:/opt/apache-maven-3.1.0/lib/jsr305-1.3.9.jar constituent[29]: file:/opt/apache-maven-3.1.0/lib/plexus-utils-3.0.10.jar constituent[30]: file:/opt/apache-maven-3.1.0/lib/aether-connector-wagon-0.9.0.M2.jar constituent[31]: file:/opt/apache-maven-3.1.0/lib/jsr250-api-1.0.jar constituent[32]: file:/opt/apache-maven-3.1.0/lib/plexus-sec-dispatcher-1.3.jar constituent[33]: file:/opt/apache-maven-3.1.0/lib/maven-core-3.1.0.jar constituent[34]: file:/opt/apache-maven-3.1.0/lib/maven-model-builder-3.1.0.jar constituent[35]: file:/opt/apache-maven-3.1.0/lib/maven-settings-builder-3.1.0.jar constituent[36]: file:/opt/apache-maven-3.1.0/lib/slf4j-api-1.7.4.jar constituent[37]: file:/opt/apache-maven-3.1.0/conf/logging/ --------------------------------------------------- Exception in thread "main" java.lang.NoSuchMethodError: org.apache.maven.execution.MavenSession.getRepositorySession()Lorg/sonatype/aether/RepositorySystemSession; at org.eclipse.tycho.core.maven.utils.PluginRealmHelper.execute(PluginRealmHelper.java:92) at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.getDependencyMetadata(P2TargetPlatformResolver.java:144) at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.setupProjects(P2TargetPlatformResolver.java:126) at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.setupProject(DefaultTychoDependencyResolver.java:87) at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:77) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:414) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:357) {code} > 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, 10 months

1
0
0 / 0

[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: --------------------------------------- Although JBIDE-15281 is fixed, I don't see how the version of Maven that is used in order to build JBoss Tools affects the behavior of this plugin. Can you tell me more? > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-961) Support CDI Extensions in Furnace

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-961?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-961: --------------------------------------- In 2.0.0.Alpha8, extensions are called in other addons, however it looks like the AddonRegistry ignores the registration of beans with the same type (different instances) > Support CDI Extensions in Furnace > --------------------------------- > > Key: FORGE-961 > URL: https://issues.jboss.org/browse/FORGE-961 > Project: Forge > Issue Type: Feature Request > Components: Furnace (Container) > Affects Versions: 2.0.0.Alpha5 > Reporter: George Gastaldi > Fix For: 2.x Future > > > Furnace should support loading of CDI extensions between multiple addons, that is, a CDI extension registered in addon A should be loaded if addon B depends on A. -- 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, 10 months

1
0
0 / 0

[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: ---------------------------------------- JBT builds are not yet supported in Maven 3.1.0. JBIDE-15281 needs to be fixed to accomplish that > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1053) Create a Spring Furnace container

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1053?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1053: ----------------------------------- Summary: Create a Spring Furnace container (was: Create a Spring Furnace Container) > Create a Spring Furnace container > --------------------------------- > > Key: FORGE-1053 > URL: https://issues.jboss.org/browse/FORGE-1053 > 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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues July 2013