Hmm, I and Aslak had some offline discussions recently, he actually developed a prototype and we came to the conclusion that that's the way to go but we can hide it under an xjavadoc cover. Basically he used javacc and its visitor-based system to traverse source files and add Xdoclet-annotated @tags to the source. It's something we need for the GUI tool recently I spoke about. But we did a brain storming and found out that we can actually hide this push model under a nice accessor API and we also noticed that we can actually replace Sun's Javadoc Doclet API with ours! So that's the whole story. Started from a little prototype to test validity of the path and ended in something huge :-)
I'm sure Aslak will enlighten you more when he has something to commit :-) Ara. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:xdoclet-devel- > [EMAIL PROTECTED]] On Behalf Of Andrew Stevens > Sent: Friday, November 16, 2001 1:47 AM > To: [EMAIL PROTECTED] > Subject: Re: [Xdoclet-devel] CVS update: 'xjavadoc - Imported sources' > > A wise old hermit known only as Ara Abrahamian > <[EMAIL PROTECTED]> once said: > > > Log Message: > > Created a new module: xjavadoc > > > > Status: > > > > Vendor Tag: XDoclet > > Release Tags: v0_1 > > > > N xjavadoc/readme.txt > > "A sub-project of XDoclet to create a better and more extensible/flexible > javadoc doclet engine mainly for GUI tools." > > Care to enlighten us, Ara? > > > Andrew. > > _______________________________________________ > Xdoclet-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-devel _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
