On Fri, Sep 25, 2009 at 4:09 PM, Ludovic Claude
ludovic.cla...@laposte.net wrote:
Yes, I mentioned that, although it is possible that you need to rebuild
tomcat6 as well as some of its dependent packages. Can you try to locate
which jars are loaded from maven-repo?
Jakub Skoczen a écrit
Hi Ludovic,
I don't see the new packages being available in testing yet, at least
not on danish mirrors. I'll upgrade and test them as soon as they are.
On Thu, Sep 24, 2009 at 10:15 PM, Ludovic Claude
ludovic.cla...@laposte.net wrote:
Yes, this version should fix this bug. It works for me,
that this entry has to be there. Ludovic, didn't
you mention rebuilding the packages so jars from maven-repo are no
longer referenced?
On Fri, Sep 25, 2009 at 11:53 AM, Michael Koch konque...@gmx.de wrote:
On Fri, Sep 25, 2009 at 11:35:17AM +0200, Jakub Skoczen wrote:
Hi Ludovic,
I don't see the new
On Fri, Sep 25, 2009 at 2:53 PM, Jakub Skoczen ja...@indexdata.dk wrote:
Ok, I have checked the packages from unstable and they work fine -
that was expected, as the 02debian.policy is updated with a maven
entry. When I take the entry out, webapps break in the same way. I'm
not sure if you
Hi Ludovic,
Enabling all security privileges to /usr/share/maven-repo/ did the
trick. Still, I don't fully understand why this is needed - shouldn't
the maven repository be only used for building stuff (like source
packages)? Why does a running tomcat instance even know about it and
tries to load
The workaround with turning off the security manager via command line
options or by granting all privileges to all code bases (mentioned by
Heikki) seems to work.
Still, since the /manager dies with a specific security exception I
tried adding a policy file for the manager only. Unfortunately the
6 matches
Mail list logo
