May 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1326) Furnace proxies should attempt to honor Thread interrupted state.

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1326?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reassigned FORGE-1326: ----------------------------------------- Assignee: Lincoln Baxter III > Furnace proxies should attempt to honor Thread interrupted state. > ------------------------------------------------------------------ > > Key: FORGE-1326 > URL: https://issues.jboss.org/browse/FORGE-1326 > Project: Forge > Issue Type: Feature Request > Components: Furnace (Container) > Affects Versions: 2.0.0.Beta3 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.x Future > > > Currently, there is no real way to force executed commands or methods to halt. Forge proxies should attempt to make this possible by checking Thread.interrupted() and throwing InterruptedException when appropriate. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1641) Build command fails when project is created inside a transaction

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1641?page=com.atlassian.jira.plugin... ] George Gastaldi reopened FORGE-1641: ------------------------------------ > Build command fails when project is created inside a transaction > ---------------------------------------------------------------- > > Key: FORGE-1641 > URL: https://issues.jboss.org/browse/FORGE-1641 > Project: Forge > Issue Type: Bug > Components: Build Tools - Maven > Affects Versions: 2.1.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Minor > Fix For: 1.4.5.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1641) Build command fails when project is created inside a transaction

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1641?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1641. ---------------------------------- Fix Version/s: 2.2.0.Final (was: 1.4.5.Final) Resolution: Done > Build command fails when project is created inside a transaction > ---------------------------------------------------------------- > > Key: FORGE-1641 > URL: https://issues.jboss.org/browse/FORGE-1641 > Project: Forge > Issue Type: Bug > Components: Build Tools - Maven > Affects Versions: 2.1.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Minor > Fix For: 2.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1742) When having a build command in a script, it times out

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1742?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1742. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.5.1.Final (was: 2.x Future) Resolution: Done Increased default timeout value to 500 > When having a build command in a script, it times out > ----------------------------------------------------- > > Key: FORGE-1742 > URL: https://issues.jboss.org/browse/FORGE-1742 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.4.1.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.5.1.Final > > > Let's say you have a long scripts with several commands (creating a project, generating entities, scaffolding rest/jsf...), at the end, if you have a {{build}} command, there is a time-out message : > {code} > [TalkEndpoint.java]$ build ; > ***ERROR*** ConferenceJSFApplication.fsh: timed out. > [Devoxx]$ ***SUCCESS*** Build Success > {code} > Nothing special in the logs, the Maven build is ok, and the app is built. But because the {{build}} command takes time to execute, it displays a time out message -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1629) Being able to add comments to a script

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1629?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1629. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.5.1.Final (was: 2.x Future) Resolution: Done The comment token is #, other tokens won't work > Being able to add comments to a script > -------------------------------------- > > Key: FORGE-1629 > URL: https://issues.jboss.org/browse/FORGE-1629 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.1.1.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.5.1.Final > > > In Forge 1 we could add comments to a script, which was very handy. It had this syntax : > {code} > @/* Forge 2.x Script */ ; > @/* Generates the draft of the application */ ; > clear ; > export ACCEPT_DEFAULTS=true ; > track-changes ; > @/* ========================== */; > @/* == Creating the project == */; > @/* ========================== */; > project-new --named pluralsight-persistence --topLevelPackage com.pluralsight.persistence.module07 --type war --finalName module07 ; > @/* ========================= */; > @/* == Setting up the model == */; > @/* ========================== */; > jpa-setup ; > constraint-setup ; > {code} > It would be nice to be able to add comments. Either with this syntax, or a more Java syntax : > {code} > /** == Setting up the model == */ > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1784) When having a scaffold-generate command in a script, it times out

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1784?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1784. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.5.1.Final (was: 2.x Future) Resolution: Done Increased default timeout value to 500 > When having a scaffold-generate command in a script, it times out > ----------------------------------------------------------------- > > Key: FORGE-1784 > URL: https://issues.jboss.org/browse/FORGE-1784 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.5.0.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.5.1.Final > > > I have a long script with several commands and at the end, when I scaffold JSF pages, the script times out : > {code} > [CD.java]$ scaffold-setup ; > ***SUCCESS*** CDI has been installed. > ***SUCCESS*** EJB has been installed. > ***SUCCESS*** Servlet API has been installed. > ***SUCCESS*** JavaServer Faces has been installed. > ***SUCCESS*** Scaffold was setup successfully. > [CD.java]$ scaffold-generate --webRoot admin --targets org.agoncal.training.javaee6adv.* ; > ***ERROR*** 02-Forge/generate.fsh: timed out. > [agoncal-training-javaee6-advanced]$ ***SUCCESS*** Scaffold was generated successfully. > {code} > Nothing special in the logs. But because the {{scaffold-generate}} command takes time to execute, it displays a time out message. The worse is that it displays {{***ERROR***}} and then {{***SUCCESS***}}. At the end of the day, my JSF artifacts are created, but the script ends and it doesn't execute the commands that follow. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1784) When having a scaffold-generate command in a script, it times out

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1784?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-1784: ------------------------------------------ Increasing the time out works. Maybe the default timeout should be increased {code} [agoncal-training-javaee6-advanced]$ run script.fsh --timeout 500 {code} > When having a scaffold-generate command in a script, it times out > ----------------------------------------------------------------- > > Key: FORGE-1784 > URL: https://issues.jboss.org/browse/FORGE-1784 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.5.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > I have a long script with several commands and at the end, when I scaffold JSF pages, the script times out : > {code} > [CD.java]$ scaffold-setup ; > ***SUCCESS*** CDI has been installed. > ***SUCCESS*** EJB has been installed. > ***SUCCESS*** Servlet API has been installed. > ***SUCCESS*** JavaServer Faces has been installed. > ***SUCCESS*** Scaffold was setup successfully. > [CD.java]$ scaffold-generate --webRoot admin --targets org.agoncal.training.javaee6adv.* ; > ***ERROR*** 02-Forge/generate.fsh: timed out. > [agoncal-training-javaee6-advanced]$ ***SUCCESS*** Scaffold was generated successfully. > {code} > Nothing special in the logs. But because the {{scaffold-generate}} command takes time to execute, it displays a time out message. The worse is that it displays {{***ERROR***}} and then {{***SUCCESS***}}. At the end of the day, my JSF artifacts are created, but the script ends and it doesn't execute the commands that follow. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1742) When having a build command in a script, it times out

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1742?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-1742: ------------------------------------------ Increasing the time out works. Maybe the default timeout should be increased {code} [Devoxx]$ run script.fsh --timeout 500 {code} > When having a build command in a script, it times out > ----------------------------------------------------- > > Key: FORGE-1742 > URL: https://issues.jboss.org/browse/FORGE-1742 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.4.1.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > Let's say you have a long scripts with several commands (creating a project, generating entities, scaffolding rest/jsf...), at the end, if you have a {{build}} command, there is a time-out message : > {code} > [TalkEndpoint.java]$ build ; > ***ERROR*** ConferenceJSFApplication.fsh: timed out. > [Devoxx]$ ***SUCCESS*** Build Success > {code} > Nothing special in the logs, the Maven build is ok, and the app is built. But because the {{build}} command takes time to execute, it displays a time out message -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1782) Errors reported on the CLI when failures occur do not log or show enough information to determine a root cause

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1782?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1782. ------------------------------------- Assignee: Lincoln Baxter III Fix Version/s: 2.5.1.Final (was: 2.x Future) Resolution: Done Closed as this specific issue was due to not properly catching exceptions when Furnace services can't be instantiated. Not sure if this needs to be fixed in Furnace or not. > Errors reported on the CLI when failures occur do not log or show enough information to determine a root cause > -------------------------------------------------------------------------------------------------------------- > > Key: FORGE-1782 > URL: https://issues.jboss.org/browse/FORGE-1782 > Project: Forge > Issue Type: Bug > Components: UI - Shell, Usability > Affects Versions: 2.5.0.Final > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.5.1.Final > > > The attached project, when installed, causes all commands to fail. The error message is reported as a Failed to Proxy Type exception, but the root cause is not shown in either the console or the forge log. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1781) UI Commands with unparameterized @Injected UIInput fields cause all commands to fail

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1781?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1781. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.5.1.Final (was: 2.x Future) Resolution: Done > UI Commands with unparameterized @Injected UIInput fields cause all commands to fail > ------------------------------------------------------------------------------------ > > Key: FORGE-1781 > URL: https://issues.jboss.org/browse/FORGE-1781 > Project: Forge > Issue Type: Bug > Components: UI - API, UI - Eclipse, UI - IntelliJ IDEA, UI - Shell, Usability > Affects Versions: 2.5.0.Final > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.5.1.Final > > Attachments: javaee7-batch.zip > > > The attached project, when installed, causes all commands to fail. The error message is reported as a Failed to Proxy Type exception, but the root cause is not shown. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues May 2014