Re: [Cp-tools-discuss] Re: Patch Manager

[Mark Wielaard]

Hi,

On Thu, 2002-05-09 at 05:09, Alex Lancaster wrote:
> >>>>> "JS" == Julian Scheid <address@hidden> writes:
> 
> Can you confirm the (C) assignment issue, Mark, then I'll just add you
> as a project developer, and you can commit all your own patches to CVS
> and close them in the Patch Manager... ;-)

Yes, a copyright assignment paper is on file with the FSF for GNU
Classpath. Brian Jones or Nic Ferrier should be able to verify that.

> JS> Note that I'll work on (patched) Gjdoc tomorrow for a couple of
> JS> hours and will try to do frequent checkins. You may want to keep
> JS> an eye on address@hidden Let me know if you also play
> JS> with it tomorrow, if you do we should avoid fixing the same bug
> JS> twice.

Good. I have subscribed to the commit list.
There is still much to learn for me about the code.
So what I want to do now first is write a very simple doclet that just
sorts the packages, classes and methods and outputs them as plain text
and have a couple of small test classes/packages that can be used as
regression tests. (I found a bug where when the return type of the
method is an array it does not seem to get the correct dimension, but I
am afraid to try to fix that without some simple regression test suite.)

This might also be done with the xmldoclet, but then I would also need
to understand XSLT better and it would add an extra point where bugs can
creep in the test framework.

To get this working correctly we will also need to update the build
architecture. Currently I just compile by hand with gcj since I don't
really understand the Makefile. I understand that Nic Ferrier has
something called automakejar, but I have not investigated it yet. Is
that what we want to use?

My ultimate goal is to use gjdoc for generating nice looking javadoc for
GNU Classpath and later with the texidoclet to generate something which
might resemble something like a real manual for it.

Cheers,

Mark