I'm using Eclipse and Jetty. Back when I first started using Tapestry, I had ALL my code in on .war file. This made it easy to make use of the class reloading feature, which is to edit a java class\tml, and the effect takes place almost instantly !
But now my application is very modular, I have like 4 different modules deployed interchangeably for different clients and I'm serving them all at the same time. So to test a Tapestry web app, I configure different run configurations, each configuration having it's related modules (.jar) in it's class-path. Here comes the problem. When I edit my code, and build my module into a .jar file, the build is broken because the .jar file is already used by the loaded web app in jetty. So I can't make use of the class-reloading feature. And even if I do no include jars and just use Eclipse's projects. I have to edit almost all my modules by annotating them, to explicitly state the modules they depend on. This is VERY annoying and wastes a lot of time. I sometimes make mistakes so it could really waste a lot of time. Has anyone faced a similar situation and would care to share a better environment setup ? *---------------------* *Muhammad Gelbana* http://eg.linkedin.com/in/mgelbana/
