Filip,
I know I don't count, but since the build is broken when running the
security manager I would have to say
> [x] Broken
To have a build that breaks an application because the container is
violating security policy looking for a non-existent file is just not
acceptable.
In order for me to use this build I would have to install the patch, and
recompile to have a working installation. This is what I'm doing right
now to run 5.5.26.
Filip Hanik - Dev Lists wrote:
The candidates binaries are available here:
http://people.apache.org/~fhanik/tomcat/tomcat-5.5/v5.5.27/
According to the release process, the 5.5.27 tag is:
[ ] Broken
[ ] Alpha
[ ] Beta
[ ] Stable
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
George Sexton
MH Software, Inc.
Voice: +1 303 438 9585
URL: http://www.mhsoftware.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
