The OpenJDK project is about 95% of a complete Java implementation. That last 5% or so is what we've called 'encumbrances', code which we weren't able to open source. The last two weeks has seen a lot of interesting movement to clearing the encumbrances. I don't know whether a comprehensive list of the encumbrances have been posted, unfortunately, but what's been cleared is significant. The following are what I found in a brief scan of the mailing list archives [security-dev 00016]: Crypto has been added to OpenJDK "We have just added the cryptographic code (aka JCE) to the OpenJDK source tree. This includes the framework (javax.crypto and friends), the SunJCE provider, and the crypto portions of the SunPKCS11 and SunMSCAPI providers." status of 6532373 (xcb_xlib.c:50: xcb_xlib_unlock: Assertion 'c->xlib.lock' failed.) is not the clearing of an encumbrance, but it is significant nonetheless. The XCB team has redesigned Xlib and it has been included in X.org's latest release, which will then be included in future versions of various operating systems. AWT and certain other applications have been crashing with those Xlib implementations, which is forcing a rewrite these applications.Read David's complete post: http://weblogs.java.net/blog/robogeek/archive/2007/10/openjdk_encumbr.html
Blogs: OpenJDK encumbrances being cleared
David Herron discusses the most recent advances in the OpenJDK project, related to code which is more difficult to classify as open source .
- Posted by: Daniel Rubio
- Posted on: October 07 2007 15:27 EDT