I thought I sent a very similar email only a couple of days earlier, but never saw it come through. Anyway, here are my thoughts, and what I've done so far.
I'm using the XJavaDoc API directly rather than through XDoclet, and this seems to work really great (10x better than JavaDoc's API). I am using Velocity templates to create the HTML output. I started working through the templates yesterday, and it seemed relatively straight forward. From what I've read, the XDoclet templating isn't as good as other templating engines, and I'm familiar with Velocity templating.
I've found 2 issues so far:
1. XJavaDoc does not read package.html to provide XDoc objects on the XPackage. If I figure out a decent way to do this, I'll submit a patch.
2. XJavaDoc is not including line-feeds in the comment text. I came across this because some JavaDoc we had used the <pre> tag, and everything appeared on one line. Same thing, if I work this out, I'll send in a patch.
Both items most welcome. Remember to write a JUnit test for your patches, and they're likely to be committed very fast (and due credits given of course).
Aslak
As for the linking, I was planning to create a templating object that would take the appropriate class/package and create a link. We expect to deal with some cross-project linking issues, so I needed to do this anyway.
------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
