Oh just listen to yourselves! We should run the unit tests every time we build using ant, that is the official way to build James.
Anything anyone does with any other tools is not our concern, we can't control it so we should step back from getting involved. If running the tests is a problem because of the time taken, then we should solve that problem first. Not just give up. One way to achieve this would be to break james out into many small library "projects", that way you can narrow your focus to a single area by depending upon the jars of the things you don't want to change and therfore don't want to test. its what we do at work but we use Maven because the repository plays a key part in this. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
