September 2015 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGEPLUGINS-30) Add eap plugin

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-30?page=com.atlassian.jira.p... ] James Perkins reassigned FORGEPLUGINS-30: ----------------------------------------- Assignee: (was: James Perkins) > Add eap plugin > -------------- > > Key: FORGEPLUGINS-30 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-30 > Project: Forge Plugins/Addons > Issue Type: Feature Request > Components: JBoss AS Addon > Reporter: Pete Muir > > Essentially a clone of the as7 plugin with the --version option described in FORGE-508 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-47) AS7 plugin loses handle when "forge restart" is issued

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-47?page=com.atlassian.jira.p... ] James Perkins updated FORGEPLUGINS-47: -------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > AS7 plugin loses handle when "forge restart" is issued > ------------------------------------------------------ > > Key: FORGEPLUGINS-47 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-47 > Project: Forge Plugins/Addons > Issue Type: Feature Request > Reporter: George Gastaldi > Assignee: James Perkins > > The following sequence of commands reproduce the problem: > {code} > as7 start > as7 status > forge restart > as7 status > {code} > If you run "as7 start", it will start as7 again using the same port. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-115) Wildfly/AS plugin should be able to "run" the current application

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-115?page=com.atlassian.jira.... ] James Perkins reassigned FORGEPLUGINS-115: ------------------------------------------ Assignee: (was: James Perkins) > Wildfly/AS plugin should be able to "run" the current application > ----------------------------------------------------------------- > > Key: FORGEPLUGINS-115 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-115 > Project: Forge Plugins/Addons > Issue Type: Bug > Components: JBoss AS Addon > Reporter: Lincoln Baxter III > Priority: Minor > > This would involve starting the server, doing a deployment, reporting errors, and opening the default browser to the correct deployment path. > New file changes should be sync'd to the deployment (exploded deployment,) and debug mode should pick up the new changes. > Shutdown would also be required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-190) The default version of WildFly should be 8.2.0.Final instead of 8.1.0.Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-190?page=com.atlassian.jira.... ] James Perkins reassigned FORGEPLUGINS-190: ------------------------------------------ Assignee: (was: James Perkins) > The default version of WildFly should be 8.2.0.Final instead of 8.1.0.Final > --------------------------------------------------------------------------- > > Key: FORGEPLUGINS-190 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-190 > Project: Forge Plugins/Addons > Issue Type: Enhancement > Components: JBoss AS Addon > Reporter: Antonio Goncalves > > When you setup WildFly 8 using all the defaults : > {code} > as-setup --server wildfly8 > {code} > The installed version is 8.1.0.Final but it should be 8.2.0.Final, the last one -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-189) The as-setup command should give the version of the server

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-189?page=com.atlassian.jira.... ] James Perkins reassigned FORGEPLUGINS-189: ------------------------------------------ Assignee: (was: James Perkins) > The as-setup command should give the version of the server > ---------------------------------------------------------- > > Key: FORGEPLUGINS-189 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-189 > Project: Forge Plugins/Addons > Issue Type: Enhancement > Components: JBoss AS Addon > Reporter: Antonio Goncalves > > The {{as-setup}} command has a {{server}} parameter. When pressing TAB the completion shows the app server with version : > {code} > $ as-setup --server > jbossas7 wildfly8 > {code} > But this is confusing because when you choose the appserver, you have the {{version}} parameter : > {code} > $ as-setup --server wildfly8 --version > 8.0.0.Alpha1 8.0.0.Alpha4 8.0.0.Final 8.1.0.Final 9.0.0.Beta1 > 8.0.0.Alpha2 8.0.0.Beta1 8.1.0.CR1 8.2.0.Final 9.0.0.Beta2 > 8.0.0.Alpha3 8.0.0.CR1 8.1.0.CR2 9.0.0.Alpha1 9.0.0.CR1 > {code} > For clarity the {{server}} parameter should only show the app server without version number : > {code} > $ as-setup --server > jbossas wildfly > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2492) forge hangs on AbstractProjectCommand.getSelectedProject() when used inside fabric8-forge (the REST service)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2492?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2492: ---------------------------------------- Just added a {{org.apache.maven.log_transfer}} system variable in Furnace 2.22.4-SNAPSHOT. See http://github.com/forge/furnace/commit/4f61059ec Can you test with this version? > forge hangs on AbstractProjectCommand.getSelectedProject() when used inside fabric8-forge (the REST service) > ------------------------------------------------------------------------------------------------------------ > > Key: FORGE-2492 > URL: https://issues.jboss.org/browse/FORGE-2492 > Project: Forge > Issue Type: Feature Request > Affects Versions: 2.17.0.Final, 2.19.2.Final > Environment: using the fabric8-forge docker image inside OpenShift > Reporter: James Strachan > > Here's a stack trace: > https://gist.github.com/jstrachan/741d65b7dd87ca0e701e > when using Forge from the hawtio console, the JVM seems to hang for 1-2 minutes now inside the call to AbstractProjectCommand.getSelectedProject(). Whats odd is I can create an archetype and invoke this code path on startup just fine - but then thats in a different thread to the one using Forge from inside the JAXRS service; so am wondering if its related to which thread is being used? > Seems to ultimately be a wagon / aether issue; taking too long to download things. > Wonder is there any way to configure the maven addon in forge to register a Wagon listener maybe? No idea whats causing the pause -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2492) forge hangs on AbstractProjectCommand.getSelectedProject() when used inside fabric8-forge (the REST service)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2492?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2492: ---------------------------------------- We could add a system property to log the output. This lagginess in the startup may be due to downloading the necessary dependencies for the project. > forge hangs on AbstractProjectCommand.getSelectedProject() when used inside fabric8-forge (the REST service) > ------------------------------------------------------------------------------------------------------------ > > Key: FORGE-2492 > URL: https://issues.jboss.org/browse/FORGE-2492 > Project: Forge > Issue Type: Feature Request > Affects Versions: 2.17.0.Final, 2.19.2.Final > Environment: using the fabric8-forge docker image inside OpenShift > Reporter: James Strachan > > Here's a stack trace: > https://gist.github.com/jstrachan/741d65b7dd87ca0e701e > when using Forge from the hawtio console, the JVM seems to hang for 1-2 minutes now inside the call to AbstractProjectCommand.getSelectedProject(). Whats odd is I can create an archetype and invoke this code path on startup just fine - but then thats in a different thread to the one using Forge from inside the JAXRS service; so am wondering if its related to which thread is being used? > Seems to ultimately be a wagon / aether issue; taking too long to download things. > Wonder is there any way to configure the maven addon in forge to register a Wagon listener maybe? No idea whats causing the pause -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2492) forge hangs on AbstractProjectCommand.getSelectedProject() when used inside fabric8-forge (the REST service)

by James Strachan (JIRA)

[ https://issues.jboss.org/browse/FORGE-2492?page=com.atlassian.jira.plugin... ] James Strachan commented on FORGE-2492: --------------------------------------- FWIW this does seem to be just a startup issue; after one project is created; the next ones all initialise fairly quickly > forge hangs on AbstractProjectCommand.getSelectedProject() when used inside fabric8-forge (the REST service) > ------------------------------------------------------------------------------------------------------------ > > Key: FORGE-2492 > URL: https://issues.jboss.org/browse/FORGE-2492 > Project: Forge > Issue Type: Feature Request > Affects Versions: 2.17.0.Final, 2.19.2.Final > Environment: using the fabric8-forge docker image inside OpenShift > Reporter: James Strachan > > Here's a stack trace: > https://gist.github.com/jstrachan/741d65b7dd87ca0e701e > when using Forge from the hawtio console, the JVM seems to hang for 1-2 minutes now inside the call to AbstractProjectCommand.getSelectedProject(). Whats odd is I can create an archetype and invoke this code path on startup just fine - but then thats in a different thread to the one using Forge from inside the JAXRS service; so am wondering if its related to which thread is being used? > Seems to ultimately be a wagon / aether issue; taking too long to download things. > Wonder is there any way to configure the maven addon in forge to register a Wagon listener maybe? No idea whats causing the pause -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2492) forge hangs on AbstractProjectCommand.getSelectedProject() when used inside fabric8-forge (the REST service)

by James Strachan (JIRA)

[ https://issues.jboss.org/browse/FORGE-2492?page=com.atlassian.jira.plugin... ] James Strachan commented on FORGE-2492: --------------------------------------- I wonder if there's a way to enable logging of aether / wagon when the maven facet is building the project so we can more easily see why its hanging? > forge hangs on AbstractProjectCommand.getSelectedProject() when used inside fabric8-forge (the REST service) > ------------------------------------------------------------------------------------------------------------ > > Key: FORGE-2492 > URL: https://issues.jboss.org/browse/FORGE-2492 > Project: Forge > Issue Type: Feature Request > Affects Versions: 2.17.0.Final, 2.19.2.Final > Environment: using the fabric8-forge docker image inside OpenShift > Reporter: James Strachan > > Here's a stack trace: > https://gist.github.com/jstrachan/741d65b7dd87ca0e701e > when using Forge from the hawtio console, the JVM seems to hang for 1-2 minutes now inside the call to AbstractProjectCommand.getSelectedProject(). Whats odd is I can create an archetype and invoke this code path on startup just fine - but then thats in a different thread to the one using Forge from inside the JAXRS service; so am wondering if its related to which thread is being used? > Seems to ultimately be a wagon / aether issue; taking too long to download things. > Wonder is there any way to configure the maven addon in forge to register a Wagon listener maybe? No idea whats causing the pause -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-212) Can't install or build the Picketlink Add-On into Forge

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-212?page=com.atlassian.jira.... ] George Gastaldi closed FORGEPLUGINS-212. ---------------------------------------- Resolution: Done > Can't install or build the Picketlink Add-On into Forge > ------------------------------------------------------- > > Key: FORGEPLUGINS-212 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-212 > Project: Forge Plugins/Addons > Issue Type: Bug > Components: Picketlink Addon > Environment: JBoss Forge, version [ 2.19.2.Final ] - JBoss, by Red Hat, Inc. [ http://jboss.org/forge ] > Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T07:57:37-04:00) > Reporter: Tim Mulle > Assignee: George Gastaldi > > I was trying to install the Picketlink Add-on provided at: > [http://forge.jboss.org/addon/org.picketlink.tools.forge:picketlink-forge-...] > However, I tried 2 ways and both fail. > 1. The recommended way on the page of: > addon-install-from-git --url https://github.com/picketlink/picketlink-forge-addon.git --coordinate org.picketlink.tools.forge:picketlink-forge-addon > I get the following error: > [ERROR] Non-resolvable import POM: Could not find artifact org.jboss.forge:forge-bom:pom:2.22.0.Final in releases > So, I tried to manually build the Add-On from GIT following the instructions on that same page and when I issue the > "build --notest clean install" step it begins to work and then fails with an error: > [SEVERE] Failed to execute goal org.jboss.forge.furnace:furnace-maven-plugin:2.7.2.Final:generate-dot (generate-dot) on project picketlink-forge-addon-spi: Execution generate-dot of goal org.jboss.forge.furnace:furnace-maven-plugin:2.7.2.Final:generate-dot failed: A required class was missing while executing org.jboss.forge.furnace:furnace-maven-plugin:2.7.2.Final:generate-dot: org/eclipse/aether/spi/connector/Transfer$State -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues September 2015