EucalyptusInMainSpec
Launchpad Entry: server-karmic-eucalyptus-in-main
Created:
Contributors:
Packages affected:
Summary
This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec. See also CategorySpec for examples.
Release Note
This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)
It is mandatory.
Rationale
This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.
User stories
Assumptions
Design
Total 99 packages to move, 34 hibernate/JBoss related
Package list (not from eucalyptus-javadeps)
Package needed |
Dependencies of dependencies |
antlr3 |
libstringtemplate-java |
libasm-java |
libow-util-ant-tasks-java |
libasm2-java |
|
libavalon-framework-java |
|
libc3p0-java |
|
libcglib2.1-java |
libaspectwerkz2-java libjrexx-java libjarjar-java libtrove-java |
libcommons-cli-java |
|
libcommons-fileupload-java |
|
libcommons-io-java |
|
libcommons-jxpath-java |
|
groovy |
antlr, libclassworlds-java, junit4 |
libgoogle-collections-java |
|
libhibernate-annotations-java |
glassfish-toplink-essentials |
libhibernate-commons-annotations-java |
|
libhibernate-entitymanager-java |
libhibernate-validator-java, libjboss-common-java libslide-webdavclient-java |
libhibernate3-java |
liboscache-java, libproxool-java, libswarmcache-java, libjboss-jmx-java, libjboss-system-java, libjboss-cache1-java libjboss-cache2-java libjgroups-java libconcurrent-java libjboss-j2ee libjdbm-java libjboss-aop-java libjboss-server-java libjcip-annotations-java libexml-java libgetopt-java libjboss-profiler-java libjboss-xml-binding-java libjboss-remoting-java libjboss-serialization-java libjboss-web-services-java libjboss-vfs-java libjboss-microcontainer-java libjboss-reflect-java libquartz-java libjboss-managed-java |
janino |
|
libjavassist-java |
|
libjibx-java |
libwoodstox-java |
libmockobjects-java |
|
libslf4j-java |
|
libxml-commons-external-java |
|
libxml-security-java |
|
libxstream-java |
libjoda-time-java libjettison-java |
glassfish-javaee |
|
libehcache-java |
libjsr107cache-java |
libasm3-java |
|
libqdox-java |
|
libcommons-attributes-java |
|
libaopalliance-java |
|
libjamon-java |
|
libxmlbeans-java |
|
jruby1.0 |
Packages from eucalyptus-javadeps
Package |
MIR Notes |
Annogen |
Abandoned |
AspectJ Weaver |
|
Axiom |
|
Axis2 |
|
Backport Util Concurrent 3.1 |
|
Drools |
|
ECJ JDT Core 3.3 |
Already in main, other version |
MVEL |
|
Google Web Toolkit |
|
HttpComponents Core |
|
Jetty 6 |
|
Jetty GWT servlet |
|
JUG (ASL) |
|
Mule |
|
Apache WS Neethi |
|
OpenSAML 1.1/Java |
OpenSAML 1.1 kinda sucks |
Rampart 1.3 |
|
Spring |
|
SWT-GTK 3.2.1 |
Already in main, other version |
Woden |
|
WSS4J |
|
Apache WS XmlSchema |
Implementation
Package refactoring
- Hibernate/JBoss stuff should be as separated as possible to try to avoid getting 34 deps of deps
Avoid greedy things when possible
- hibernate: +33
- libcglib2.1-java: +4
- groovy: +3
Size matters
- groovy: 2Mb
- libxmlbeans-java: 2.3Mb
- jruby-1.0: 3.5Mb
- libjgroups-java: 3Mb
- libhibernate3-java: 2.2Mb
- glassfish-toplink-essentials: 2.4Mb
- libquartz-java: 0.8Mb
Spring from debian
Removes
- AspectJWeaver
Adds
- libjdo-api-java
- libfreemarker-java
- velocity
- libjexcelapi-java
- libstruts1.2-java
- glassfish-appserv
- libibatis-java (multiverse)
- libtomcat5.5-java
Test/Demo Plan
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.
This need not be added or completed until the specification is nearing beta.
Unresolved issues
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.