I also use these targets in all ant files init clean compile build test javadoc The build targets always creates the artefact, no matter whether it is a jar or war or whateveer. You should also include structural things in your conventions like a shared repository for all libraries (versioned by some VCS). Another thing would be to define properties for your jar versions i.g.
: lib. Commons-collections=commons-collections-2.1. Jar lib. Commons-io=commons-io-1.4. Jar which are referenced in all ant files, common.
Jar is a place where artifacts are placed in case other projects depend on them.... For deployment I use another set of ant files deploy_component-name. Xml After years with ant I would recommend to keep the number of targets limited, sometimes you may have a few more steps for code generation etc. To see how others handle bigger projects you could download the source distribution of an application server to examine how they do this job.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.