I will, but now I'm moving houses and I don't have much access to
Internet and my dev box is in another country. This is in my todo list
for November, there is a small issue to fix in maven-repo-helper, then I
will fix tomcat.
Ludovic
Michael Koch a écrit :
On Mon, Sep 28, 2009 at
On Mon, Sep 28, 2009 at 10:26:07AM +0200, Jakub Skoczen wrote:
On my machine all jars under /usr/share/maven-repo/javax are real
files and not symlinks. That includes Servlet, JSP and Expression
Language APIs so stuff definitely loaded by tomcat:
|-- javax
| |-- el
| | `-- el-api
|
On my machine all jars under /usr/share/maven-repo/javax are real
files and not symlinks. That includes Servlet, JSP and Expression
Language APIs so stuff definitely loaded by tomcat:
|-- javax
| |-- el
| | `-- el-api
| | `-- 2.1
| | |-- el-api-2.1.jar
| |
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,
On Fri, Sep 25, 2009 at 11:35:17AM +0200, Jakub Skoczen wrote:
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.
It will not be in testing for at least the next 10 days as we just uploaded
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 want to pursue that anymore (they DO work now) but I
still find it weird that
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
Hi Jakub,
This was a temporary issue with the way I installed jars both to
/usr/share/java and /usr/share/maven-repo. In an old version of
maven-repo-helper, the script mh_installjar was copying the jars to
/usr/share/maven-repo and a link was created in /usr/share/java. I'm
doing now the
Hello,
On Thu, Sep 24, 2009 at 12:29:11PM +0100, Ludovic Claude wrote:
This was a temporary issue with the way I installed jars both to
/usr/share/java and /usr/share/maven-repo. In an old version of
maven-repo-helper, the script mh_installjar was copying the jars to
/usr/share/maven-repo
Yes, this version should fix this bug. It works for me, Jakub, can you
confirm that the fix works for you as well?
Ludovic
Michael Koch a écrit :
Hello,
On Thu, Sep 24, 2009 at 12:29:11PM +0100, Ludovic Claude wrote:
This was a temporary issue with the way I installed jars both to
On Thu, Sep 24, 2009 at 09:15:47PM +0100, Ludovic Claude wrote:
Yes, this version should fix this bug. It works for me, Jakub, can you
confirm that the fix works for you as well?
I have made some small changes and uploaded to the archive.
Thanks for your work.
Cheers,
Michael
--
To
Hello Heikki and Jakub,
Thanks for this detailed error report. I believe that I have fixed this
issue, by adding a grant on /usr/share/maven-repo/ in the file
02debian.policy. Can you check that it is working? If you need, I have
created a new .deb in my PPA
On Wed, Sep 09, 2009 at 09:24:12PM +0200, Marcus Better wrote:
the file /etc/inint.d/tomcat6 should be left alone, the security manager
can be disabled in /etc/default/tomcat6.
Thanks. That was just my quick workaround.
Apparently a security manager permission problem. The manager app seems
On Thu, Sep 10, 2009 at 10:57:24AM +0200, Heikki Levanto wrote:
On Wed, Sep 09, 2009 at 09:24:12PM +0200, Marcus Better wrote:
You can add the appropriate permissions in /etc/tomcat6/policy.d, but
actually I have no idea how it could work on 6.0.20-2 if the rules were
not there in the
Package: tomcat6
Version: 6.0.20-5
Severity: grave
Justification: renders package unusable
Installing tomcat6-admin on a brand new Debian/squeeze gets nothing but
a crash, when accessing the admin page. A similar crash happens when
accessing any web app.
I reproduced this on a fresh squeeze (a
16 matches
Mail list logo
