[ https://issues.jboss.org/browse/FORGE-2074?page=com.atlassian.jira.plugin... ] James Strachan updated FORGE-2074: ---------------------------------- Description: So Apache Karaf has a nice command "dev:watch *" http://karaf.apache.org/manual/latest-2.x/commands/dev-watch.html which looks at all the currently installed bundles; figures out the mvn coords and where they are in the ~/.m2/repository; then any which are SNAPSHOT versions it watches them; if they get rebuilt it auto-reloads them. It'd be great to have the same kinda thing in Forge for when you're working on an addon; then every time you do a mvn build, forge would reload it on the fly so you could try it out for real in a forge shell. Right now it seems pretty slow to install newly built addons; anything to make the development a bit more RAD would be really cool. e.g. a new command, something like... {code} addon-watch * {code} which uses the currently loaded jars and applies the wildcard to filter the SNAPSHOT builds to watch in ~/.m2/repository to detect if a build is done; then it'd invoke the addon-install command with the updated jar was: So Apache Karaf has a nice command "dev:watch *" http://karaf.apache.org/manual/latest-2.x/commands/dev-watch.html which looks at all the currently installed bundles; figures out the mvn coords and where they are in the ~/.m2/repository; then any which are SNAPSHOT versions it watches them; if they get rebuilt it auto-reloads them. It'd be great to have the same kinda thing in Forge for when you're working on an addon; then every time you do a mvn build, forge would reload it on the fly so you could try it out for real in a forge shell. Right now it seems pretty slow to install newly built addons; anything to make the development a bit more RAD would be really cool -- This message was sent by Atlassian JIRA (v6.3.1#6329)