Of Java 1.5 and Gentoo

The road to unmasking Java 1.5 has been long and arduous. There have been enough issues to warrant it’s own FAQ and an entire redesign of the way we handle Java packages.

I won’t go into detail about the specific problems incurred, as the FAQ should sufficiently cover them.

Nearly a year ago, work was begun on a new build system (ie new eclasses and a new version of java-config). About six months later, we had a new fully featured, flexible build system. Highlights include build-time VM switching, build-time build.xml rewriting, and a more flexible means of storing/setting the system and user VM.

Unfortunately, there were enough incompatibilities between this new system and the old one that we couldn’t just drop it in the tree as is. A few months were needed to determine how to best migrate to the new system, in such a way that it could be done incrementally, and it could be properly tested (ie be in ~arch). Notes about the method we choose can be found on our wiki.

Since then, a lot of work has been done to implement the migration system, as well as code and documentation cleanup.

So now, we (kartlk and I), have deemed the new system ready for prime time. This coming week, we will be finishing any last minute cleanups, and bringing in any packages that require 1.5. Once that is complete, we will be announcing the changes on the developer mailing for public scrutiny/input. Assuming that there are no issues that crop up, the new system would be brought into the main tree a week or so later.

You may begin rejoicing now.

3 thoughts on “Of Java 1.5 and Gentoo”

  1. Ohhh. This could be cool. Just last week I’d been hearing some cool things about Jam, a tiny JVM that used gnu classpath, and usually worked with jikes, but alas when I installed it there was no way to switch it over with java-config. Hopefully now this will make it possible to do so. Then we can support java, but have free implementations usable 🙂
    Thank you so much for the hard work.

  2. @Dan Ballard
    All the 1.5 stuff is pretty much unrelated to JamVM. The problem is that someone (anyone) has put in the effort to make it usable as a system/user vm, not as much that it wasn’t previously possible.

    @Srgjan Srepfler
    There are many, many issues associated with using maven to build stuff, and it is a touch subject as you mentioned. I actually go over a lot of the details in a previous entry for ideas for Google Summer of Code.

Comments are closed.