> Pending any unresolved issues, Avalon Framework should now be considered in > Code Freeze. It will remain so until the weekend is over, and I will make the > release on Monday. The only type of contributions that should be made to > Avalon 4.1 are documentation spelling fixes. The only types of changes to > the code should be Javadoc spelling fixes. > > We have the weekend to come up with any showstoppers, so fire away!
What about the latest problems with the current avalon jars in cocoon HEAD? I guess there were some classloader problems somehow related to the the DefaultConfigurationBuilder. http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=100721487530909&w=4 and http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=100737345202034&w=4 Is this issue already investigated or even solved?! -- Torsten -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
