On Tue, Mar 12, 2013 at 11:09 AM, Stephen Connolly < [email protected]> wrote:
> Also that way of using tomcat is really just relying on rebuilding the > artifacts again > AFAICT, the tomcat-maven-plugin works more-or-less the same as your jszip-maven-plugin, except it only scans the dependent projects' outputDirectory (while you also scan the POMs). At least it works as you described for jszip: when your IDE recompiles a class or otherwise copy a resource to the outputDirectory, the webapp is automatically restarted (which BTW has unfortunate side-effects if you happen to use Guice: https://github.com/tbroyer/gwt-maven-archetypes/issues/19)
