Re: [Cp-tools-discuss] Re: gjdoc

[Julian Scheid]

I have a bunch of fixes and enhancements lying around for a
couple of weeks that I should have checked in one-by-one over
time but haven't, sorry for that. They should fix Mark's
problems and a couple of other issues as well, like the
occasionally missing last character in a comment.

They also bring support for the ErrorReporter interface and
an experimental java->xml->info translator that one day may
make TexiDoclet obsolete. Also some performance improvements,
and some minor corrections to the documentation.

All in all, this is probably a major update. If noone
intervenes, I will proceed as follows during the coming days:
tag the current CVS status for gjdoc as "0.02", so that the
current version can be retrieved comfortably in case anything
goes wrong; and check in my local sources.

Note that my local version has been tested today to produce the
full docs for the latest CVS release of Classpath, and the command
line interface didn't change -  so there should be no problem
switching to this new version for the person caring about the
generated API documentation.

Pardon me for violating the golden rule. Nevertheless this
update will hopefully prove useful.

Julian


Brian Jones wrote:
> Mark Howard <address@hidden> writes:
>
> >Hi,
> >  I've been working on updated Debian packages for gjdoc, mostly
> >involving Debian specific changes. I've been doing much testing - gjdoc
> >works well most of the time; however gjdoc has trouble finding classes
> >[...]
> I don't know.  I believe we're looking for a new owner of this tool
> development-wise.  Perhaps you could enter these problems as bugs on
> Savannah?  I'm interested in fixing these things, but it is currently
> low on my priority list.
> [...]