In the April 5 JavaLobby Newsletter, the editors write:

We have a couple of new sites in development for the Javalobby network, and we have been facing the tough question of whether or not to use Java to build them? After long consideration we're close to deciding not to, at least not for the main core of the sites. Instead, we're thinking we may try out the powerful PHP content management system called Drupal. As far as we know there's nothing quite like this in the Java space, and the effort required to implement the features Drupal offers by default would take us a long time to develop in Java. It just doesn't make sense to start from scratch when there's an active community already growing around Drupal. We have looked at JetNuke, JBoss Portal, and several other Java-powered options, but as far as we can tell they are not superior for our purpose. Even if we do use Drupal, we'll still be able to use Java for back-end services and logic, and we feel the hybrid approach may allow us to get the job done faster and with less heavy lifting.

Bonus points for Drupal, I say. :-)