I haven't read all mails from this week yet, but it seems that nothing is preventing us from a release tomorrow.
Or did I oversee something?
Nothing that I'm aware of.
BTW, I already upgraded my project at work today to 2.1.5-almostReleased. My 2.1.4 logkit.xconf did no longer work because of missing this change: http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/webapp/WEB-INF/logkit.xconf?r1=1.7&r2=1.8&diff_format=h
Cocoon failed to initialize the logging. And I thought first it was the "every logger manager" commit ...
And my forms did no longer work due to a classpath issue. Cocoon delivers common collections 3.0, Tomcat has an older version of this jar in common/lib - and Tomcat seems to prefer its own one. Is that correct behaviour? How shall I get my version of a jar in the webapp to be used? Not every webapp has a paranoid classloader ... thanks again to Sylvain for that nice piece of work :)
Joerg
