Re: GNU Jaxp patch

[Mark Wielaard <mark at klomp dot org>]

On Fri, 2005-01-28 at 17:54 -0700, Tom Tromey wrote:
> Tom> I thought about this, since you mentioned it on irc.  I'm not so sure
> Tom> though.  We've used this directory setup for a long time (note that
> Tom> while I updated org.xml.sax.* and org.w3c.*, many of these classes
> Tom> have been in the tree for years -- Anthony checked them in on
> Tom> 11-7-2001).
> 
> I forgot to mention, actually I don't feel very strongly about this;
> it just looked like a nuisance to change it all around.  If other gcj
> maintainers can agree on a preference, I will implement it.  If not, I
> think I will let inertia be my guide.

I do feel strongly about this. Since we are actively merging and making
sure the GNU Classpath and libgcj prjects become more similar I do feel
it is import that we do it in the same way. It was a mistake in the past
to import an external package without clearly marking it as external. We
have an opertunity now to fix that. Since GNU Classpath does import
external packages by following the GNU Maintainers Guidelines in. If you
are going to do it different from how we do it in GNU Classpath then I
want at least to make sure that we agree on a way to do it and
restructure the GNU Classpath repository to be similar to the libgcj
one. But please consider doing it like we already have in GNU Classpath
since:

- It makes sure GNU Classpath/libgcj are merged more and don't diverge
  more on "little" details. And such things add up and make going
  towards a fully merged project harder.
- It will automatically give you the correct layout to show users that
  these are externally imported projects with their own distribution
  terms and README files explaining how/if they differ from upstream.
- Makes merging with upstream and GNU Classpath more clear.
- Follows the GNU Maintainer Guidelines for these kind of issues.
- Doesn't upset the GNU Classpath maintainer that he isn't seen as a
  libgcj maintainer even though the projects claim to be merged/merging.

Thanks,

Mark

Attachment: signature.asc
Description: This is a digitally signed message part