Personally, I follow the Maven build pattern - I first gather the contents of the WAR in a single directory location, then I package up the whole directory. That way I have both a packaged WAR file and an "exploded" WAR directory.
I did learn a LONG time ago that it's best to make project directories either read-only or write-only, regardless of the build system you're using. I normally build an exploded WAR and feed that directly to Tomcat for debugging, then jar up the exploded WAR when I want to make a distribution module. In keeping with not having permanent files in an output directory, I copy them from a static file source directory (or directories) into the exploded WAR directory when I do a build, just as I compile to the exploded WAR's WEB-INF/classes directory.
A lot the of modern-day software development platforms are designed to permit parcelling out work to those with the best aptitude for it. A lot of modern-day business is predicated on making one person do all the work, regardless of aptitude.
ant does not allow using <copy> in <war> block, you may use
in your ant file. and then just create a "WEB-INF" directory in "any-dir" directory, and put xml files there.
the directory structure would be like this:
+any-dir
+WEB-INF
<xml-files-are-here>
that's how i did it.
This message was edited 2 times. Last update was at by Ali Qanavatian
who is this guy anyway?
Michael Henderson
Greenhorn
Joined: Feb 22, 2011
Posts: 2
posted
0
why not use the webinf element. This works for me.
This message was edited 1 time. Last update was at by Michael Henderson
0
