[mojo-dev] [jira] (MGWT-375) process-resources required to pick up changes in either dev mode

[Thomas Broyer (JIRA)]

Title: Message Title

Thomas Broyer edited a comment on an issue   Re: process-resources required to pick up changes in either dev mode You can use a third-party tool to automatically run {{mvn process-resources}} whenever a file changes, e.g. https://github.com/facebook/watchman That said, this is something that could also be built into the plugin, like JSZip does in jszip:run: http://jszip.org/jszip-maven-plugin/run-mojo.html Wondering though whether this shouldn't be the job of the IDE/editor: Eclipse does this automatically AFAICT, can't really tell for IntelliJ IDEA but I suppose "Make" would do it, and I suspect some "more than the simplest" editors could do it too, or just a keyboard shortcut away. Patches welcome! Add Comment   Mojo's GWT Maven Plugin / MGWT-375 process-resources required to pick up changes in either dev mode In both gwt:run-codeserver and gwt:run, code changes made in a non-maven-aware text editor are not picked up until mvn process-resources is run. I understand the argument for not watching resources, but why not trigger a code server recompile on updates to source files? (Or, at least, allow the option.) I'm used to being able to refresh to see code ... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email