A wise old hermit known only as Aslak Hellesy <[EMAIL PROTECTED]> once said:
> After a discussion with Ara yesterday, we decided that it's time to > start replacing com.sun.javadoc with xjavadoc in the xdoclet source. I > have created a new branch named XJAVADOC_REFACTORING for this. > > PLEASE TRY TO AVOID ADDING/COMMITTING ANYTHING TO THE XDOCLET CORE > UNTIL THE REFACTORING IS DONE. > > It's a very big job, so I would like to warn you all that this might > take some time ... In which case, might it not be better to first concentrate on sorting out bugs (and the valueobjects) and adding more unit tests for a 1.1.3 release (say, around the end of the month), and do the xjavadoc integration once it's as robust as we can make it? There's almost 50 open tracker items at the moment, plus a couple of messages in xdoclet-user complaining that 1.1.2 broke things that worked previously... Of course, since there's the new branch it doesn't necessarily hold up the refactoring work, but if we've got to hold off on stuff in the main branch till that's done then what's the point of the branch? It might as well go straight into the main code. > The first > step is to get things to compile, the second is to verify that > everything works as before. > > It's important that as many as possible can participate in the second > step, as nobody knows all parts an dark corners of xdoclet anymore. The > refactoring will most likely introduce some bugs, so let's kill them > together. Unit tests, and plenty of them :-) Let's get a comprehensive suite of tests done first, and there'll be less work needed to find the bugs later. Andrew. _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
