Danny,
> > This is test code and thus shouldn't be wrapped up with the production > > deliverable. > > it can be in the o.a.james package, surely, just excluded from james.jar. For the Java files, that would be fine. That means that an appropriate modification to the build.xml should be included with any future submission of the test-suite. > In any case packaging test cases so that users can also use them is no bad > thing, as the tests evolve we can use them to allow people to make better > bug reports. I don't have an objection to packaging test suites so users can (if they so choose) use them. I do have an objection to bundling them in with the .jar required for a basic production system. There are a number of very good reasons why you need to be able to keep them separate. I also have an objection to contaminating the src/java directory with batch and user-modifiable configuration files. --Peter -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
