Bug#212863: new java policy: ok or not?

[Jan Schulz <jasc.usenet@gmx.de>]

Hallo,

There seems to be no more questions, but unfortunatelly nonone has
said something like 'do it' or 'file bugs with patches' or 'go
testing' or whatever until now.

I'm a little scared to go on, and ask Stefan for the temporary
inclusion of the findjava and other scripts in java-common or the VM
and package maintainer to include java-config-files, without such
comments..

Also, I would like to start working on a patch for mpkg-j2sdk to
include all the changes and to make the new policy bits working with
the new policy.

Aparat from the naming convention for the jar files, I can't see any
'conflicts' when having both policy implemented (and that's no big
deal...). That's why I would like to take the same steps like the
recent "resolvconf transition", and supply patches, which supports
both versions of policy. At first I will get in changes for runtime
matters and finish with the 'ant-environment' changes at build-time.

So, what I would like to hear is not a 'seconded' as required for a
policy change, but something like 'lets see some testing and if
successful we can go on and change the policy' from some debian
developers.

Looking at the list of Java package maintainerns, I would like to get
the ok from at least some of (hopefully all maintainer with more than
two packages with 'Depends: .*java.*' and who represent ~70% of the
java packages):

Arnaud Vandyck
Stefan Gybas
Takashi Okamoto
Ola Lundqvist
Ben Burton
Mark Johnson
Adam Majer
Stephen Zander
Robert Bihlmeyer
Stephen Zander
Tollef Fog Heen  
Grzegorz Prokopski 

I'm especially interested in the OK from Arnaud, Stefan, Takashi and
Ola, who are representing more than 50% of the above list.

Nice greetings, Jan
-- 
Jan Schulz                     jasc@gmx.net
     "Wer nicht fragt, bleibt dumm."