Torsten Curdt wrote:
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.
Cocoon does not use the DefaultConfigurationBuilder. It uses the
SAXConfigurationBuilder directly. Now that the SAXConfigurationBuilder
is back to the way it was, it will be fixed.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
