Danny Angus wrote:
This is somewhat perpendicular to this, but could have an impact...I'd like to see a formal proposal, so we can have a synopsis of why we need to change things, debate the benefits and drawbacks of competing systems are, and, if we don't reach concensus, a vote.I'm susceptable to persuasion on all counts, including retaining the status-quo (ant & xslt) and would like to hear someone make the case for change. Otherwise it would seem to be change for change's sake, or keeping up with the Joneses. d.
The tests we have right now (they don't compile, but that notwithstanding) are functional tests, not unit tests.
So last night I created a new directory and build tasks for junit tests on the individual classes in James. This was primarily driven by wanting to unit test ExtraDotOutputStream, and we can use this test build task for over unit tests as they get written.
Adding this prompted me to do some renaming in the build.xml since between the multiple javadocs, multiple source code locations, etc..., the naming conventions were becoming somewhat confusing. For example, the intermediate build directories are named "build.[something]" while the source directories are named "[something].dir".
Anyway, I'm pretty sure I've broken where the javadocs get created, but if we're going to just scrap all of that, then maybe it's not important for me to fix it before I commit.
--
Serge Knystautas
Lokitech
Software - Strategy - Design
http://www.lokitech.com
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
