Jan Schulz wrote:
Here is the discussed proposal java policy as txt and also as tar.gz archive, including all written scripts and manpages
As I've already mentioned in http://lists.debian.org/debian-java/2003/debian-java-200309/msg00124.html you (or anybody else) can't replace the whole Java Policy. You need to submit individual proposals for the individual changes (e.g. the naming of JARs in /usr/share/java or the use of your tools) and you need people (strictly speaking Debian developers) who second your proposals. Just because nobody complained when you posted your last proposal does not mean that everybody agrees. I have not seen anybody who has seconded your proposal (maybe I missed a few mails?).
The process for changes to the the Java Policy is not different than the process for the Debian Policy (/usr/share/doc/debian-policy/policy-process.txt.gz in the debian-policy package). Please remember, we don't have the constitutional power to force other Debian developers to implement the specification. Changes can only be made if (most of) the people that have to implement it agree. The situation is even worse since the Blackdown package are not part of Debian at all, so they are not forced to follow the Java Policy.
java-config and java-config(1)java-config-update and java-config-update(1) java-config-file(5)findjava, findjava(1), findjavarc(5) and a test script dh_java (with inline manpage)
I can include these in the java-common package but I will not replace the Java Policy. These scripts need to prove their usability first before they can be made mandatory.
Stefan