[JBoss JIRA] (FORGE-1742) When having a build command in a script, it times out
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1742:
----------------------------------------
Summary: 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 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-1741) Arquillian addon should be bundled by default on Forge
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1741?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-1741:
-------------------------------------
Description:
If the life cycle of an application is :
* Code (/)
* Test (x)
* Deploy (x)
Then Arquillian Addon should be bundled by default
was:
If the life cycle of an application is :
* Code
* Test
* Deploy
Then Arquillian Addon should be bundled by default
> Arquillian addon should be bundled by default on Forge
> ------------------------------------------------------
>
> Key: FORGE-1741
> URL: https://issues.jboss.org/browse/FORGE-1741
> Project: Forge
> Issue Type: Enhancement
> Components: Addon Development
> Affects Versions: 2.4.1.Final
> Reporter: Antonio Goncalves
>
> If the life cycle of an application is :
> * Code (/)
> * Test (x)
> * Deploy (x)
> Then Arquillian Addon should be bundled by default
--
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-1740) JBoss AS addon should be bundled by default on Forge
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1740?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-1740:
-------------------------------------
Description:
If the life cycle of an application is :
* Code (/)
* Test (x)
* Deploy (x)
Then I think it's important to have a JBoss AS addon bundled with Forge.
was:I think it's important to have a JBoss AS addon bundled with Forge. Now, we can generate an application out of the box, but we cannot deploy it.
> JBoss AS addon should be bundled by default on Forge
> ----------------------------------------------------
>
> Key: FORGE-1740
> URL: https://issues.jboss.org/browse/FORGE-1740
> Project: Forge
> Issue Type: Enhancement
> Components: Addon Manager
> Affects Versions: 2.4.1.Final
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> If the life cycle of an application is :
> * Code (/)
> * Test (x)
> * Deploy (x)
> Then I think it's important to have a JBoss AS addon bundled with Forge.
--
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-1740) JBoss AS addon should be bundled by default on Forge
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1740:
----------------------------------------
Summary: JBoss AS addon should be bundled by default on Forge
Key: FORGE-1740
URL: https://issues.jboss.org/browse/FORGE-1740
Project: Forge
Issue Type: Enhancement
Components: Addon Manager
Affects Versions: 2.4.1.Final
Reporter: Antonio Goncalves
Fix For: 2.x Future
I think it's important to have a JBoss AS addon bundled with Forge. Now, we can generate an application out of the box, but we cannot deploy it.
--
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-1739) Installing JBoss AS addon swallows commands
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1739:
----------------------------------------
Summary: Installing JBoss AS addon swallows commands
Key: FORGE-1739
URL: https://issues.jboss.org/browse/FORGE-1739
Project: Forge
Issue Type: Bug
Components: Scaffold
Affects Versions: 2.4.1.Final
Reporter: Antonio Goncalves
Fix For: 2.x Future
Installing the JBoss AS Addon from https://github.com/jerr/as-forge-addon/ swallows commands. Just after installation, when I press TAB I just get the following commands :
{code}
ll alias unalias export
{code}
Then, I restart Forge, press TAB once, the commands appear, press TAB a second time, not more commands (except {{ll alias unalias export}}).
--
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