June 2016 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2665) addon-watch command for developer mode where we can make the forge container watch for rebuilds of addons and auto-reload them

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2665?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2665: ----------------------------------- Component/s: Addon Development > addon-watch command for developer mode where we can make the forge container watch for rebuilds of addons and auto-reload them > ------------------------------------------------------------------------------------------------------------------------------ > > Key: FORGE-2665 > URL: https://issues.jboss.org/browse/FORGE-2665 > Project: Forge > Issue Type: Feature Request > Components: Addon Development > Reporter: James Strachan > > its kinda clumsy and slow when working on a Forge addon; you try some code, rebuild it, then in your Forge app you run the remove / install commands to get the new code into your CLI install of Forge (or your web app running Forge, or your IDE etc...) > What would be cooler is if we had an 'addon-watch wildcard' command. That lets you start/stop watching addons that have SNAPSHOT versions. Even ignore the wildcard and just watch all SNAPSHOT addons. > When watching, every installed addon of version SNAPSHOT, we'd watch ~/.m2/repository for the builds of the addons. If you then rebuild an addon, it'd reload the addon automatically (remove it first, then re-install it)! > This would make it much quicker and simpler to try things out! Its especially painful when testing out changes to Forge commands in a web app (e.g. hawtio-forge) as you typically need to build the addons then rebuild the addon repo then rebuild/restart the web app etc! > So this simple approach would help folks get more rapid feedback on building any addon - however you run them (CLI, web, IDE) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2665) addon-watch command for developer mode where we can make the forge container watch for rebuilds of addons and auto-reload them

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2665?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2665: ---------------------------------------- I'll have a look at it. Thank you! > addon-watch command for developer mode where we can make the forge container watch for rebuilds of addons and auto-reload them > ------------------------------------------------------------------------------------------------------------------------------ > > Key: FORGE-2665 > URL: https://issues.jboss.org/browse/FORGE-2665 > Project: Forge > Issue Type: Feature Request > Reporter: James Strachan > > its kinda clumsy and slow when working on a Forge addon; you try some code, rebuild it, then in your Forge app you run the remove / install commands to get the new code into your CLI install of Forge (or your web app running Forge, or your IDE etc...) > What would be cooler is if we had an 'addon-watch wildcard' command. That lets you start/stop watching addons that have SNAPSHOT versions. Even ignore the wildcard and just watch all SNAPSHOT addons. > When watching, every installed addon of version SNAPSHOT, we'd watch ~/.m2/repository for the builds of the addons. If you then rebuild an addon, it'd reload the addon automatically (remove it first, then re-install it)! > This would make it much quicker and simpler to try things out! Its especially painful when testing out changes to Forge commands in a web app (e.g. hawtio-forge) as you typically need to build the addons then rebuild the addon repo then rebuild/restart the web app etc! > So this simple approach would help folks get more rapid feedback on building any addon - however you run them (CLI, web, IDE) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2665) addon-watch command for developer mode where we can make the forge container watch for rebuilds of addons and auto-reload them

by James Strachan (JIRA)

[ https://issues.jboss.org/browse/FORGE-2665?page=com.atlassian.jira.plugin... ] James Strachan commented on FORGE-2665: --------------------------------------- we could yeah - I"d be happy just doing the addon-remove / addon-lnstall TBH to start with ;) I guess JRebel would be much faster; but could end up with jboss modules issues possibly? > addon-watch command for developer mode where we can make the forge container watch for rebuilds of addons and auto-reload them > ------------------------------------------------------------------------------------------------------------------------------ > > Key: FORGE-2665 > URL: https://issues.jboss.org/browse/FORGE-2665 > Project: Forge > Issue Type: Feature Request > Reporter: James Strachan > > its kinda clumsy and slow when working on a Forge addon; you try some code, rebuild it, then in your Forge app you run the remove / install commands to get the new code into your CLI install of Forge (or your web app running Forge, or your IDE etc...) > What would be cooler is if we had an 'addon-watch wildcard' command. That lets you start/stop watching addons that have SNAPSHOT versions. Even ignore the wildcard and just watch all SNAPSHOT addons. > When watching, every installed addon of version SNAPSHOT, we'd watch ~/.m2/repository for the builds of the addons. If you then rebuild an addon, it'd reload the addon automatically (remove it first, then re-install it)! > This would make it much quicker and simpler to try things out! Its especially painful when testing out changes to Forge commands in a web app (e.g. hawtio-forge) as you typically need to build the addons then rebuild the addon repo then rebuild/restart the web app etc! > So this simple approach would help folks get more rapid feedback on building any addon - however you run them (CLI, web, IDE) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2665) addon-watch command for developer mode where we can make the forge container watch for rebuilds of addons and auto-reload them

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2665?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2665: ---------------------------------------- Yeah, that would be awesome. Perhaps we can use JRebel? > addon-watch command for developer mode where we can make the forge container watch for rebuilds of addons and auto-reload them > ------------------------------------------------------------------------------------------------------------------------------ > > Key: FORGE-2665 > URL: https://issues.jboss.org/browse/FORGE-2665 > Project: Forge > Issue Type: Feature Request > Reporter: James Strachan > > its kinda clumsy and slow when working on a Forge addon; you try some code, rebuild it, then in your Forge app you run the remove / install commands to get the new code into your CLI install of Forge (or your web app running Forge, or your IDE etc...) > What would be cooler is if we had an 'addon-watch wildcard' command. That lets you start/stop watching addons that have SNAPSHOT versions. Even ignore the wildcard and just watch all SNAPSHOT addons. > When watching, every installed addon of version SNAPSHOT, we'd watch ~/.m2/repository for the builds of the addons. If you then rebuild an addon, it'd reload the addon automatically (remove it first, then re-install it)! > This would make it much quicker and simpler to try things out! Its especially painful when testing out changes to Forge commands in a web app (e.g. hawtio-forge) as you typically need to build the addons then rebuild the addon repo then rebuild/restart the web app etc! > So this simple approach would help folks get more rapid feedback on building any addon - however you run them (CLI, web, IDE) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2665) addon developer mode where we can make the forge container watch for rebuilds of addons and auto-reload them

by James Strachan (JIRA)

James Strachan created FORGE-2665: ------------------------------------- Summary: addon developer mode where we can make the forge container watch for rebuilds of addons and auto-reload them Key: FORGE-2665 URL: https://issues.jboss.org/browse/FORGE-2665 Project: Forge Issue Type: Feature Request Reporter: James Strachan its kinda clumsy and slow when working on a Forge addon; you try some code, rebuild it, then in your Forge app you run the remove / install commands to get the new code into your CLI install of Forge (or your web app running Forge, or your IDE etc...) What would be cooler is if we had an 'addon-watch wildcard' command. That lets you start/stop watching addons that have SNAPSHOT versions. Even ignore the wildcard and just watch all SNAPSHOT addons. When watching, every installed addon of version SNAPSHOT, we'd watch ~/.m2/repository for the builds of the addons. If you then rebuild an addon, it'd reload the addon automatically (remove it first, then re-install it)! This would make it much quicker and simpler to try things out! Its especially painful when testing out changes to Forge commands in a web app (e.g. hawtio-forge) as you typically need to build the addons then rebuild the addon repo then rebuild/restart the web app etc! So this simple approach would help folks get more rapid feedback on building any addon - however you run them (CLI, web, IDE) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2665) addon-watch command for developer mode where we can make the forge container watch for rebuilds of addons and auto-reload them

by James Strachan (JIRA)

[ https://issues.jboss.org/browse/FORGE-2665?page=com.atlassian.jira.plugin... ] James Strachan updated FORGE-2665: ---------------------------------- Summary: addon-watch command for developer mode where we can make the forge container watch for rebuilds of addons and auto-reload them (was: addon developer mode where we can make the forge container watch for rebuilds of addons and auto-reload them) > addon-watch command for developer mode where we can make the forge container watch for rebuilds of addons and auto-reload them > ------------------------------------------------------------------------------------------------------------------------------ > > Key: FORGE-2665 > URL: https://issues.jboss.org/browse/FORGE-2665 > Project: Forge > Issue Type: Feature Request > Reporter: James Strachan > > its kinda clumsy and slow when working on a Forge addon; you try some code, rebuild it, then in your Forge app you run the remove / install commands to get the new code into your CLI install of Forge (or your web app running Forge, or your IDE etc...) > What would be cooler is if we had an 'addon-watch wildcard' command. That lets you start/stop watching addons that have SNAPSHOT versions. Even ignore the wildcard and just watch all SNAPSHOT addons. > When watching, every installed addon of version SNAPSHOT, we'd watch ~/.m2/repository for the builds of the addons. If you then rebuild an addon, it'd reload the addon automatically (remove it first, then re-install it)! > This would make it much quicker and simpler to try things out! Its especially painful when testing out changes to Forge commands in a web app (e.g. hawtio-forge) as you typically need to build the addons then rebuild the addon repo then rebuild/restart the web app etc! > So this simple approach would help folks get more rapid feedback on building any addon - however you run them (CLI, web, IDE) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2664) basic web app with forge

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-2664: ----------------------------------------- Summary: basic web app with forge Key: FORGE-2664 URL: https://issues.jboss.org/browse/FORGE-2664 Project: Forge Issue Type: Quality Risk Environment: *Location*: http://forge.jboss.org/documentation *User-Agent*: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36 *Referrer*: http://forge.jboss.org/ *Screen Resolution*: 1360 x 768 Reporter: Lincoln Baxter III Tried to do the steps throughout the basic web app but it failed in: [Speaker.java]$ scaffold-generate --web-root / ***INFO*** Required inputs not satisfied, entering interactive mode [0] ( ) AngularJS [1] ( ) Faces Press <ENTER> to confirm, or <CTRL>+C to cancel. * Scaffold Type: [0-1] 1 ? Web Root Path (The web root path where the scaffolding will be placed/accessible from the client browser (default '/').) [/]: [0] ( ) org.basic.java.web.app.model.Speaker Press <ENTER> to confirm, or <CTRL>+C to cancel. * Targets (The JPA entities to use as the basis for generating the scaffold.): [0] ? Facelet Template (The Facelets template file to be used in the generated facelets.): 2.2 ***ERROR*** Targets must be specified. [Speaker.java]$ *Reporter*: Mateus Souza da Silva *E-mail*: [mailto:rhinoceroshead@gmail.com] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2663) GIT commands should be camel cased

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2663: -------------------------------------- Summary: GIT commands should be camel cased Key: FORGE-2663 URL: https://issues.jboss.org/browse/FORGE-2663 Project: Forge Issue Type: Enhancement Components: Git Affects Versions: 3.2.2.Final Reporter: George Gastaldi Assignee: George Gastaldi Priority: Minor Fix For: 3.2.3.Final The GIT commands are uppercased, it would be nice to have them camel-cased. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2663) GIT commands should be camel cased

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2663?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2663. ---------------------------------- Resolution: Done > GIT commands should be camel cased > ---------------------------------- > > Key: FORGE-2663 > URL: https://issues.jboss.org/browse/FORGE-2663 > Project: Forge > Issue Type: Enhancement > Components: Git > Affects Versions: 3.2.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Minor > Fix For: 3.2.3.Final > > > The GIT commands are uppercased, it would be nice to have them camel-cased. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2662) NullPointerException while running unit tests

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2662?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2662. ---------------------------------- Resolution: Done > NullPointerException while running unit tests > --------------------------------------------- > > Key: FORGE-2662 > URL: https://issues.jboss.org/browse/FORGE-2662 > Project: Forge > Issue Type: Bug > Components: Developer Tools - Java > Affects Versions: 3.2.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 3.2.3.Final > > > {code} > Caused by: java.lang.NullPointerException > at org.jboss.forge.addon.devtools.java.RegisterAsServiceCommand.<init>(RegisterAsServiceCommand.java:56) > at org.jboss.forge.addon.devtools.java.RegisterAsServiceCommand_$$_javassist_df00c6d4-a6a4-452d-b881-6c8146c5d723.<init>(RegisterAsServiceCommand_$$_javassist_df00c6d4-a6a4-452d-b881-6c8146c5d723.java) > Caused by: java.lang.NullPointerException > at org.jboss.forge.addon.devtools.java.JavaEqualsHashcodeCommand.<init>(JavaEqualsHashcodeCommand.java:63) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2016