Update: The New Java Hotness

Just to keep people updated about how the new Java stuff is going… it’s going pretty good 😀

A lot of smaller kinks have been worked out, better documentation, more useful error / warnings, and such forth. All in all, there has been a lot of good input and feedback.Most of the issues users have been running into is not having everything unmasked and keyworded properly. With unmasking,the former will no longer be an issue.

So, I hope to go forward with unmasking over the long (read: 4 1/2 days) weekend. At that point, we’ll begin switching packages over to using the new eclasses, doing version bumps, bug squashing, and all that jive.

The New Java Hotness

I’m pleased to announce that the new Java hotness has finally hit the tree 🙂 It’s currently in package.mask, but I expect to unmask it in the next few days.

To begin using it, you will need to add the appropriate entries to /etc/portage/package.unmask, and then follow the upgrade guide.

For those not familar with that this means, here are some highlights:

  • Ability to switch the current VM on the fly
  • Changes to the user and system VM take effect immediately, and no
    longer are tied to the shell environment (ie no more running env-update &&
    source /etc/profile after switching the sytem VM)
  • Now has the concept of a