One of the most simple ways to do this is to deploy to a myapp.war directory in your deploy dir, instead of actually creating a war file. I usually have two targets in my build script. One which I use 99% of the time which doesn't actually jar / war / war anything, just copies files to directories, and the other which does actually create nice pretty ear / war / jar packages. The really great thing about going with the first option while in development is that ant and maven only copy files which there have been updated copies of. So you can really get the build to test cycle pretty short.
I hope that helps. -James View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3834003#3834003 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3834003 ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
