Integration of Ehcache in Ubuntu

Registered by Jos Boumans

With the 10.10 release, we would like to integrate Ehcache into Ubuntu. This includes upgrading it to 2.1, pushing it to main, and start packaging the Terracotta stack to lead to the Clustered Cache feature.

Blueprint information

Jos Boumans
Thierry Carrez
Thierry Carrez
Series goal:
Accepted for maverick
Milestone target:
milestone icon ubuntu-10.10-beta
Started by
Thierry Carrez
Completed by
Thierry Carrez

Related branches



Abandoned the idea of packaging demo, since it doesn't really make sense as a package. No feedback from terracotta on the packaging, spec considered completed.

maverick-alpha-3: 2
ubuntu-10.10-beta: 1

Work items for maverick-alpha-2:
[alex-snaps] Perform dependency analysis for ehcache-2.1: DONE
Package missing build dependencies for Ehcache 2.1: DONE
Initial ehcache-2.1.0 packaging in PPA: DONE
Set appropriate targets for spec based on Terracotta's feedback: DONE
Check ehcache-core 2.1.0 compat with existing packages: DONE
Upload ehcache 2.1.0 in Debian or Ubuntu: DONE

Work items for maverick-alpha-3:
[alex-snaps] Provide description of needed binaries for terracotta server (by July 8th): DONE
[alex-snaps] Provide description of needed binaries for dev console (by July 8th): DONE
[alex-snaps] Provide description of tomcat example L1 application (by July 29th): DONE
Split/package design: DONE
Test package, evaluate necessary improvements: DONE
Fix dependencies so that dev console runs on top of a full JRE, add launcher for dev-console: DONE
Default config in /etc for terracotta-server, FHS compliance: DONE
Run as specific user, add upstart script to terracotta server: DONE
Publish to RPA / Announcement : DONE

Work items for ubuntu-10.10-beta:
Integrate terracotta feedback (no feedback yet): POSTPONED

mathiaz review / 20100526:
 - I would focus on upgrading ehcache to 2.1 as this is what we have the most insight on.
   - Agreed, fixed WI. Complexity=2 for the A2 targets, will reevaluate goals for A3.
 - We're lacking more insight on the terracotta stack and have WI defined for investigating what is required there.
   Depending on the outcome of the analysis I would create new specs/WI further down the road instead of using random "Target X" WI.

jib review / 20100526:
 * Suggested priority: 1
 * Suggested Subcycle: Every, staying in sync with Ehcache release
 * I'm not understanding what target 1/2/3 represent
   * Those were placeholders, as we are still missing Terracotta's evaluation on dependencies. I removed them. We'll review targets for A3 based on A2 experience --ttx
 * I'd like to see individual work items that are owned by upstream as well
   * Added that --ttx


Work Items

This blueprint contains Public information 
Everyone can see this information.