A package java-common is created, containing this policy and some basic tools.
Virtual packages are created: java-compiler, java2-compiler, java-virtual-machine, java1-runtime and java2-runtime.
Packages written in Java are separated in two categories: programs and libraries. Programs are intended to be run by end-users. Libraries are intended to help programs to run and to be used by developers. Both must depend on java-virtual-machine.
Both are shipped as Java bytecode (*.class files, packaged in a *.jar archive) and with an "Architecture: all" since Java bytecode is supposed to be portable.
This policy does not yet address the issue of documentation (for instance HTML pages made with javadoc).
Java virtual machines must provide java-virtual-machine and depend on java-common. They can also provide the runtime environment that the package contains (java1-runtime and/or java2-runtime). If it does not provide the files itself it must depend on the needed runtime environment.
I should use /etc/alternatives for the name 'java' if they are command-line compatible with the Sun's java program.
They should have a CLASSPATH predefined which include the needed runtime environment.
If a given source (like the JDK does) brings both a compiler and a virtual machine, you may name the compiler package xxxx-dev.