Cleanups for java libraries in main for LTS

Registered by Thierry Carrez on 2009-11-09

Lots of Java libraries were added to main following introduction of Eucalyptus in karmic. Since lucid is LTS, we need to review what can be done to clean up before committing to support those for 5 years. We also need to ensure that the Lucid java libraries stack is sufficient for (and fully compatible with) the expected Eucalyptus 1.7.

Blueprint information

Status:
Complete
Approver:
Jos Boumans
Priority:
Medium
Drafter:
Thierry Carrez
Direction:
Approved
Assignee:
Thierry Carrez
Definition:
Approved
Series goal:
Accepted for lucid
Implementation:
Implemented
Milestone target:
milestone icon lucid-alpha-3
Started by
Thierry Carrez on 2009-12-11
Completed by
Thierry Carrez on 2010-02-12

Related branches

Sprints

Whiteboard

Secondary engineer: zulcss

Review mdz 2009-11-30: This seems to combine three areas of work: general java library packaging work (e.g. updates, GWT, GCJ), Eucalyptus dependencies (should be part of the eucalyptus packaging spec instead) and Jetty packaging work (e.g. promoting it to main, no rationale?)
ttx 2009-11-30 -- I re-centered this spec on "java library packaging cleanup work", moving eucalyptus-1.7-related things to the relevant spec (eucalyptus-commons-ext is a java library, separate from eucalyptus, so cleanups in that area are kept here). Added detailed rationale to make it clearer that the jetty work is really about cleaning up some code duplication.
mdz 2009-11-30 -- looks good, approved

Status:
Completed.

Work items for lucid-alpha-3:
(1) Ask Eucalyptus upstream if we can get rid of jruby build-dep in eucalyptus-commons-ext: DONE
(1) Test jetty package from debian: DONE
(1) Enable tests in jetty package, as much as possible: DONE
(1) Jetty MIR: DONE
(1) Review jetty MIR comments and apply necessary fixes: DONE
(1) Phase out jetty6, cglib2.1 (pending archive management): DONE
(1) Get eucalyptus-commons-ext to build with cglib2.2: DONE
(1) Demote jruby1.2 to universe: DONE
Check that GWT can build with swt-3.5 (answer is YES): DONE
If yes, switch to swt-3.5 build-depend for GWT (sprint): DONE
Discuss best option to fix the GCJ recommendation (=no generic fix): DONE
Check/Update libbcprov-java, liblog4j1.2-java: DONE
Check/Update libantlr-java, antlr3: DONE
Check/Update libjaxp1.3-java, libxerces2-java, libxalan2-java: DONE

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.