This is as much a build environment question as an
Ant question, but here goes.
I'm on a team that is building an enterprise application - it contains
ejb's, web apps, and a couple of stand-alone client apps. They're all bundled into an ear file for deployment.
The trouble is in the build environment. We have the following directories:
src/ - all source files
lib/ - jars to use for compile and deployment
etc/ - config files
...
build.xml
We use one build.xml (for now) to build everything, with targets that can build each individual application, or the whole thing.
It's getting unmanageable, and I'm considering a different structure:
/ejb
/src/
/lib/
/etc/
/webapp1
/src/
/lib/
/etc/
/webapp2
/src/
/lib/
/etc/
/clientapp1
/src/
/lib/
/etc/
Each app will have its own build.xml, and then there will be one main build.xml at the project root that can call the other build files.
Any thoughts on this? I'd like to get feedback from people who are managing big projects.
Chris