At 11:14 AM 02/11/01, you wrote: >Where can I find good examples of how folks are architecting their Ant >builds such that a release version is built without any test code in it >whatsoever and when the tests are run the deployment is built to include the >necessary pieces for Cactus testing?
Nothing special here - I build and jar everything, test, then delete the test classes and source, rebuild. (Note that I'm obviously copying the source from somewhere else!) >Here are the issues I'm facing: > >* Some tests are non-Cactus JUnit tests. Some are Cactus. I'm separating >them by directory structure. There needs to be a distinction in the Ant >targets on which tests get run and such. How/why do you want to distinguish between them? >* web.xml allow conditional inclusion of the redirector configuration Think about setting up (i.e. building then copying a war) a test application. Then delete it. >* I do not want duplication in my build.xml Call the war building task twice, before testing, then after testing/deletion of test classes. >I'm going to start tackling these issues myself, but if its already been >implemented nicely then it'd save me some time and I'd be able to contribute >my efforts on the Cactus project in other areas! :) > > Erik > > > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- * Jim Cheesman * Trabajo: [EMAIL PROTECTED] - (34)(91) 724 9200 x 2360 In retrospect it becomes clear that hindsight is definitely overrated -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
