Friends and relations join the OpenJDK effort
So what is OpenJDK? Increasingly, it's not just the effort behind the GPL Java 7, but a collection of related projects working around that GPL code base. A few months back, Red Hat started theIced Tea project to take the existing OpenJDK source and work through the encumbrances through the use of free software from GNU Classspath. So that's a project that has started with the OpenJDK source and gone its own way, though it certainly could contribute back to the main project in the future.
Now let's consider the other direction... projects based code-bases other than OpenJDKs that nevertheless want to combine under the OpenJDK umbrella. This is happening today, as some of the BSD Java porting projects formalize their relationship with OpenJDK.
A brief note yesterday from Mark Reinhold on the OpenJDK
announce list announces the approval of an OpenJDK Porters Group, as proposed by Dalibor Topic earlier in the month. The group's introduction says, "this group exists to bundle and aid such efforts under the OpenJDK umbrella, and integrate them in the OpenJDK community through porting projects." Projects that have expressed an interest in joining the OpenJDK effort are the BSD porting projects, led by Kurt Miller and Greg Lewis, as well as Landon Fuller's much-discussed Soy Latte port of the BSD Java to Mac OS X.
Oh, and if you missed it, yesterday's feature article was all about OpenJDK, specifically, how to build it from source. Even if you're not about to build it yourself, the story of how to do it is a fun read, and it's proof positive that the source is out there for you to work with.
Also in Java Today, the Early Draft Review ends this Saturday, December 1, for JSR-299, Web Beans. "The goal of this work is to enable EJB 3.0 components to be used as JSF managed beans, unifying the two component models and enabling a considerable simplification to the programming model for web-based applications in Java. In particular, this work will provide a programming model suitable for rapid development of simple data-driven applications without sacrificing the full power of the Java EE 5 platform."
TheServerSide points out an interesting blog by Zviki Cohen on Five ways for tracing Java execution. Faced with finding bugs in code he may have partial (or no) source to, he says "I usually find that it is faster to trace the code at runtime. Especially when it comes to non-trivial links between classes, like an interface with multiple implementations which may be picked at runtime. The smörgåsbord of design time tools is just insufficient. In this post, I will summarize the common methods (I know of) for tracing the runtime execution." The five techniques considered are breakpoints, debug messages, dynamic proxy, run-time profiler, and AOP.
Where's your Java career going? Do you want to get into new stuff, or do more with what you already know? The latest java.net Poll asks "What would most help your career?" Cast your vote on the front page, then visit the results page for current tallies and discussion.