OpenJDK 6 build 12 source posted (corba, jaxp, jaxws)
Martin Buchholz
martinrb at google.com
Tue Sep 16 14:51:16 PDT 2008
Over time, I've also become a big fan of maintaining mods to
sources which are primarily maintained elsewhere, in the form of
explicit patch files, as in the debian project.
Mercurial has pretty good infrastructure to help with this,
using the Mercurial Queues extension. It has pretty good
documentation in the hgbook
http://hgbook.red-bean.com/hgbookch12.html#x16-26700012
Managing distributed development is never easy, however.
Martin
On Tue, Sep 16, 2008 at 14:43, Joseph D. Darcy <Joe.Darcy at sun.com> wrote:
> Mark Wielaard 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.
>
> -Joe
>
More information about the jdk6-dev
mailing list