On Thursday 17 January 2008, Marcus Better wrote: > Yes, see #460839 where we deal with this for the tomcat5.5-webapps. > > The stricter permissions are part of a tightened security policy. I > think our options are: > (i) Change JULI not to look for the logging.properties in those places > unless specifically configured to do it, > (ii) Give blanket permission for JULI to look up logging.properties > files in all webapps (possibly circumventing the security fix), > (iii) Leave as is and let users add the necessary permissions.
It could just catch the SecurityException while looking for logging.properties and pretend that the file doesn't exist, possibly after logging a message saying so.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
