I started by changing XJavaDoc to use QDox' parser. That went quite well, but I still had some problems getting all of XJavaDoc's tests to pass with the new QDox parser, so I never committed it.
The last week I had a crack at the other merger strategy: Add API routines to QDox that XJavaDoc has, but QDox misses. This turned out to be a lot easier. You can see some of the progress in QDox' JIRA:
http://jira.codehaus.org/secure/BrowseProject.jspa?id=10103&report=roadmap
Being the primary developer of XJavaDoc, I feel no shame when I claim that QDox is far superior to XJavaDoc when it comes to design, simplicity, performance and test coverage. As I have stated before, QDox' only drawback (from an XDoclet perspective) was the lack of a few API routines. This has now been amended (at least the most important parts), and I therefore no longer see any good reason to use XJavaDoc in XDoclet2.
Let's use QDox!
Any objections if I update XDoclet2 to use QDox?
Cheers, Aslak
-- http://blogs.codehaus.org/people/rinkrank/
------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
