Summary

This spec is about planned improvements in Java frameworks support in Ubuntu, including:

Release Note

Hibernate is now properly supported in Ubuntu main.

Rationale

Hibernate3 is in universe as of Lucid. Eucalyptus depends on hibernate but uses a stripped copy in eucalyptus-commons-ext (which is in main). This was originally done to avoid the extra work on moving to main all of Hibernate build dependencies (and dependencies of build dependencies). With ehcache potentially targeted to main, that makes two top-level stacks needing Hibernate properly supported. Now that LTS is out we can have a fresh look at the issue again.

User stories

As a Java packager, I want to properly push packages depending on Hibernate into Ubuntu main (or packages depending on Spring to Ubuntu universe). Using the Java stack available in 10.10, I can now do so.

Assumptions

Moving Hibernate to main depends on the MIR team acceptation of the related packages. Having pre-acceptation that the number (36) and the scope of packages (JBoss4/Glassfish) are not a problem would be good.

Design

Hibernate

Update to Hibernate 3.5

Hibernate 3.5 supports JPA2 so it's definitely something we want to support in the distribution. This is likely to happen in Debian through the efforts of Damien Raude-Morvan.

Move libhibernate3-java to main

One Ubuntu-specific issue is that Hibernate3 is still in universe. Eucalyptus depends on hibernate but uses a stripped copy in eucalyptus-commons-ext (which is in main). This was originally done to avoid the extra work on moving to main all of Hibernate build dependencies (and dependencies of build dependencies). Now that LTS is out we can have a fresh look at the issue again. Here is the graph of the 36 packages:

Notes:

The main blocker to expect is resistance from the MIR team to pull some high-profile source packages (jbossas4, glassfish) into main. However, the related server packages (jbossas4, glassfish-appserv) would stay in universe, which somehow reduces the impact.

Spring

Spring needs to be updated to the latest version in Debian which does not depend anymore on JRuby for building. Otherwise it will be pushed to multiverse by the forces of nature and policy.

Other

The JRuby situation needs to be tackled as it becomes more and more difficult to work around it. Debian bug 551618 tracks the necessary work on JRuby build dependencies.

Implementation

Ubuntu-specific work

See work items in server-maverick-java-frameworks whiteboard for details.

Debian-side work

Test/Demo Plan

tbd

Unresolved issues

None.

BoF agenda and discussion

UDS discussion notes

Policy:

Actions:


CategorySpec

MaverickJavaFrameworksSpec (last edited 2010-05-20 14:07:04 by lns-bzn-48f-81-56-218-246)