As for the template itself, I'm just sticking in the XJavaDoc object in the Velocity context, and if it's a package or class template, the XPackage and XClass objects as well. Then let Velocity scripting do the rest, e.g, $xclass.qualifiedName or #foreach ($interface in $xclass.interfaces) or $xclass.doc.firstSentence.
-- Serge Knystautas President Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
Laramie Crocker wrote:
Hello Serge Knystautas,
Fantastic!
I think this approach will work well.
Will you post your code to the xdoclet project somewhere? Or is it part of a private undertaking?
If you will be posting it soon, then I can wait. (Perhaps you could point me at where it will show up...) If not, then could you please provide a sample template of what kinds of things I have to do? Or perhaps there's a pertinent example of using velocity as such in the distribution? I use webmacro for everything, so velociy should be no problem for me to read.
thanks, Laramie
------------------------------------------------------- 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
