[forge-issues] [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

[James Strachan (JIRA)]

    [ https://issues.jboss.org/browse/FORGE-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256903#comment-13256903 ] 

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)