OpenJDK on FreeBSD

Ivan Voras writes (19/02/2009) that he’d love to rewrite his finstall project (FreeBSD GUI Installer) in Java, which may result in license issue. OpenJDK would be  a much more preferable option:

OpenJDK looks like it might “soon” be ported to FreeBSD (though judging by the progress it looks like the official FreeBSD Java crowd is working on OpenJDK 1.7 which has not been released yet, instead of OpenJDK 1.6, which is).

Well, as of today, OpenJDK is available for FreeBSD.

For those unacquainted with OpenJDK, OpenJDK is an open-source implementation of the Java Platform, Standard Edition. Much of the OpenJDK code is licensed under the GPL version 2 with the Classpath exception. The Java Hotspot virtual machine source code is licensed under the GPL version 2 only.

This is a small step, but may have far reaching benefits.


  1. says

    That would be the day I’ll move my desktop/notebooks to PC-BSD and servers to OpenBSD …

    Having PC-BSD and DesktopBSD installers written on Qt .. and Qt moved to LGPL … there doesn’t seem to be a good reason why a new GUI installer should be written a subpar OpenJDK, which, to make it worse, adds more GPL code to FreeBSD …

    If Ivan prefers to use OpenJDK over building upon what’s already up, running and working (PC-BSD GUI installer), good for him .. but I’m out :)

    “but Sun’s Java was (and still is) encumbered by legal obstructions of redistribution for the FreeBSD packages”

    Then why going for it when Qt is LGPL, represents no legal obstructions at all and makes the GUI installer consistent with KDE (default FreBSD desktop) ???

    If there’s stuffI don’t want on my system are: Java, Mono, Flash and Moonlight …

    A GUI installer written un Java, instead of Qt … (endless resources wasted on) ZFS instead of HAMMER .. no word on PCC … this is starting to smell funny to me …

  2. Alex Libman says

    I too am disappointed that *BSD developers aren’t taking more obvious steps to choose permissive dependencies over copyleft / restrictively-licensed ones. Apache Harmony is starting to emerge as a serious JDK contender, and there are plenty of other permissively-licensed GUI toolkits to choose from, but with 1/10th the effort you could simply code up a Web / AJAX-based interface for your project instead!

    If done right a Web-based administration interface can be fast, secure, easy to use, easy to RTFM with inline tooltips and documentation links, easy to automate, easy to extend and integrate, and accessible from a wide range of devices – from a bare-bones text-only Web browsers, to smart-phones for remote access on the go, or with an inevitable future Chromium fork that’ll be 100% copyleft-free!

Leave a Reply

Your email address will not be published. Required fields are marked *