DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=26392>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=26392 failing Cocoon 2.0.4 deployment on Tomcat 5 through broken Batik JAR [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED ------- Additional Comments From [EMAIL PROTECTED] 2004-06-01 11:55 ------- No, distributions are distributed and so remain untouched forever. It's an immutable collection of files of a specific date. The reason is simple: If we change a distribution we might break it at another place. At the end we have 5 different versions of one dist and five different errors. How shall one reference a specific version of a dist? The JAR is fixed in cocoon-2.0 CVS, but there will probably never be a final Cocoon 2.0.5 as it would be to much effort to put all the files into Apache License 2.0 - and that's a requirement by the Apache Software Foundation for released stuff since 1st March 2004. If it's possible for you, you should grab Cocoon 2.0 from CVS, maybe there are also snapshots available. Cocoon 2.0 CVS is "release ready", we only missed the deadline mentioned above to do a final release. If you need a working an released version you have to switch to Cocoon 2.1. Don't fear the build process itself in both 2.0 CVS and 2.1 releases. Especially in the latter ones it's easy to build Cocoon yourself.
