[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:
---------------------------------------
yeah; I could be using the Forge CLI on a project 'cheese'; then building plugin 'foo' somewhere else; so long as it installs into ~/.m2/repository, the Forge runtime should be able to find the installed addons and watch the local builds of it - wherever forge is running
> 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
> Assignee: George Gastaldi
>
> 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)
7 years, 10 months
[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 edited comment on FORGE-2665 at 6/24/16 12:46 PM:
-----------------------------------------------------------------
yeah; I could be using the Forge CLI on a project 'cheese'; then building addon 'foo' somewhere else; so long as it installs into ~/.m2/repository, the Forge runtime should be able to find the installed addons and watch the local builds of it - wherever forge is running
was (Author: jastrachan):
yeah; I could be using the Forge CLI on a project 'cheese'; then building plugin 'foo' somewhere else; so long as it installs into ~/.m2/repository, the Forge runtime should be able to find the installed addons and watch the local builds of it - wherever forge is running
> 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
> Assignee: George Gastaldi
>
> 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)
7 years, 10 months
[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:
----------------------------------------
Hum, nevermind. I think it should query the installed snapshots and listen for changes in there
> 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
> Assignee: George Gastaldi
>
> 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)
7 years, 10 months
[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:
----------------------------------------
Looks cool. That would be executed inside the addon sources directory, right?
> 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
> Assignee: George Gastaldi
>
> 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)
7 years, 10 months
[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:
---------------------------------------
or even start/stop ;)
> 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
> Assignee: George Gastaldi
>
> 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)
7 years, 10 months
[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:
---------------------------------------
I'd be tempted to start with
{code}
addon-watch true
addon-watch false
{code}
to turn watching on or off. A wildcard could be optional; though a good OOTB would be all SNAPSHOT versions of addons only (which there's usually not that many anyway)
> 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
> Assignee: George Gastaldi
>
> 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)
7 years, 10 months
[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:
---------------------------------------
or on/off if you prefer instead of true/false ;)
> 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
> Assignee: George Gastaldi
>
> 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)
7 years, 10 months
[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:
----------------------------------------
Some questions:
- What would be a good syntax for this command? (eg. {{addon-watch --coordinate a:b}}?)
- How would you stop this command from executing? (another command? Specify a number of times after execution?)
> 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
> Assignee: George Gastaldi
>
> 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)
7 years, 10 months
[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 reassigned FORGE-2665:
--------------------------------------
Assignee: George Gastaldi
> 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
> Assignee: George Gastaldi
>
> 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)
7 years, 10 months
[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:
---------------------------------------
awesome - thanks!
> 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)
7 years, 10 months