Aslak Helles�y wrote:
XJavaDoc is pretty mature by now. -But so is Eclipse. One of the EclipseI think this would be a very good move for XDoclet 2. This means that we do not have to maintain our own parser anymore, and that we are using code that is eyeballed by many IBM partners. Just look at the buildnotes, there are already a huge amount of bugs fixed.
modules, JDT, is an engine similar to XJavaDoc. It can be used outside the
Eclipse IDE.
The nice thing about JDT is that it has diff/merge support too (I haven't
verified this, but Erich Gamma said told me it has that). That would make it
possible to edit generated sources and not lose them.
What do you think about evaluating JDT for XDoclet 2?
Also, take a look at the Hibernator source:
http://tinyurl.com/49zk
Hibernator uses Eclipse's java parser, is fairly small, and is therefore an
excellent source of inspiration if we want to investigate this path further
for XDoclet 2.
Aslak
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
Also, as it states on the JDT home page ( http://www.eclipse.org/jdt/index.html ), JDT includes an incremental java compiler, source code formatter, indexed based search facility. Perhaps we could use this stuff for XDoclet too?
The only thing I worry about is performance. How does it compare to XJavaDoc?
Cheers,
Mathias
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
