Hi again, After playing around with options I now think there isn't much opportunity to speed things up, other than to use JRebel or change the way I develop (not start the webapp so much). The webapp project looks for jars in the maven repository not the war, so I only need to do maven install on the dom project when I change a dom class. That should have been apparent sooner :(
Bottomline: the webapp takes some time to start, but that is fine. On Fri, Jul 31, 2015 at 11:27 AM, Stephen Cameron < [email protected]> wrote: > Hi, > > I would greatly appreciate some advice on speeding up development in > Eclipse. Using the simpleapp project with separate dom, fixture, integtest > and webapp subprojects. > > I'd at least like the webserver (jetty,tomcat) to restart when I modify a > dom class. This is what I am used to with Dynamic Web Projects, however > after a bit of trying today I still cannot get that to work, using Tomcat. > > It seems most are using JRebel with IntelliJ, but I am not so keen to go > there yet as I am (re)learning on many fronts at present. > > The issue with Tomcat is a jetty dependancy, this was noted previously > [1], but I could not get around it by removing > jetty-all-9.2.11.v20150529.jar as suggested, I then got a null-pointer > exception. > > At the moment I have to rebuild the whole project after a class change in > the dom-project then restart the server to see the change. Is the because > the .war has to be rebuilt for mvn jetty:run to use the new version of the > class file? > > I've just tried to use the eclipse jetty plugin but that is telling me > that the dom classes have not been enhanced by datanucleus. > > Hoping for some insights. > > Thanks > Steve C > > > [1] http://permalink.gmane.org/gmane.comp.apache.incubator.isis.devel/9931 > > > > > > >
