Hey all.
As I said in a previous note, the current Javadoc task was unnecessarily (although very thoroughly) checking each .java fie in the source path for its package. The unfortunate part about it is that Javadoc itself can't deal with .java files in the wrong directory. So, there really isn't any need to check each and every file for its package, unless the Javadoc tool in JDK1.3 can handle this situation. I didn't check that one, to be honest, but I'm not too hopefull.
At any rate, I've created a patch that removes the scanning of individual files and simply scans the directory structure for potential packages. The name matching rules still apply.
To provide a comparison, I have a source tree with 3, 605 java files. I only need to document 63 of those files in five packages during one particular run of Javadoc. With the old Javadoc task, it took 00:01:17. With the new Javadoc task, it took 00:00:21. You decide. :-)
Glenn McAllister
Software Developer. IBM Toronto Lab, (416) 448-3805
"An approximate answer to the right question is better than the
right answer to the wrong question." - John W. Tukey
javadoc.patch
Description: Binary data
