OpenJDK 6 build 12 source posted (corba, jaxp, jaxws)
Mark Wielaard
mark at klomp.org
Wed Sep 17 02:55:31 PDT 2008
Hi Joe,
On Tue, 2008-09-16 at 14:43 -0700, Joseph D. Darcy wrote:
> In the JDK, we import some large bodies of code that are actively
> maintained elsewhere, such as the GlassFish project. This is generally
> a copy-and-paste of the upstream code, with perhaps some local fixes or
> licensing changes. This approach has the attendant code maintenance
> issues and in the future I'd like to revisit how we interact with these
> other code bases; the approach of just having the code as a build
> dependency and keeping local patches under revision control, as done in
> IcedTea, might be better overall.
Actually directly working on patches is also not very good. As Martin
suggested switching to something like mercurial queues might be a good
idea.
I think the main thing to take care of is having a more or less formal
description on how to do new imports. What is considered the canonical
upstream source, how to record a new import (version, etc), when to
import a new (stable) upstream version, and how to clearly mark any
local changes in the sources themselves if they are necessary and cannot
be pushed upstream (directly) for some reason.
Cheers,
Mark
More information about the jdk6-dev
mailing list