Ok, cool, good to know... glad to be pushing people to make the users life easier.
BTW I expect to be able to make the pom reloading stuff available for other plugins to use as a nicer API. I don't recommend copying my tricks directly as there are some hidden assumptions that I am making which I will be able to abstract away when I turn this into an API (which is part of the process of preparing 1.0-beta-1) On 12 March 2013 10:21, Thomas Broyer <[email protected]> wrote: > 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) >
