Hello Ed, Thank you for the bug report and sorry for the long delay in responding. I have been looking at this issue and trying to determine a reasonable approach given that it appears to be JVM dependent.
The easiest thing from a user perspective is to drop a symlink in /etc/tomcat6/policy.d/ to either: /etc/java-6-openjdk/security/java.policy or /etc/java-7-openjdk/security/java.policy The package can't merely add both symlinks, because tomcat won't start if the target of the symlink doesn't exist. It might be possible to remove and then recreate the symlink in tomcat6 init script after the JVM has been determined. However, I'm wondering if it would be preferable to drop to add some documentation regarding the symlink to /etc/default/tomcat6 and let the user create the symlink when he/she enables security. Thank you, tony
signature.asc
Description: OpenPGP digital signature
__ This is the maintainer address of Debian's Java team <http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. Please use debian-j...@lists.debian.org for discussions and questions.
