> From: Mark S. Kent [mailto:[EMAIL PROTECTED]]
>
> > 0. Do you use the *same* JRE to compile and run Cocoon?
>
> Yes.
>
> > 1. Check that user you use to launch tomcat can read jars:
> > chmod 666 $TOMCAT_HOME/webapps/cocoon/WEB-INF/*
> >
> > Or even: chmod -R 666 $TOMCAT_HOME/webapps/cocoon
>
> 0. Do you use the *same* JRE to compile and run Cocoon?
Yes.
> 1. Check that user you use to launch tomcat can read jars:
> chmod 666 $TOMCAT_HOME/webapps/cocoon/WEB-INF/*
>
> Or even: chmod -R 666 $TOMCAT_HOME/webapps/cocoon
All files/folders are owned by tomcat.dev. I left the permissions
> From: Mark S. Kent [mailto:[EMAIL PROTECTED]]
>
> I decided to get the src for 2.0.3 and did a build on it instead of
the
> 2.0.2 I couldn't get to work. Now I'm getting different (but somewhat
less
> arcane) errors when starting.
>
> in access.log:
> =
I decided to get the src for 2.0.3 and did a build on it instead of the
2.0.2 I couldn't get to work. Now I'm getting different (but somewhat less
arcane) errors when starting.
in access.log:
=
DEBUG (2002-07-25) 16:47.28:377 [access] (Unkn
jdk1.3.0_02, tomcat 3.2.1
Am upgrading 2.0.2 -> 2.0.3, though, as I've removed all cocoon files
from webapps and cleared out tomcat's workfiles, effectively it's a
new install.
build runs through ok, and installs war in webapps (tried both 'build
install' and 'build installwar'). When I start
