we were reviewing licenses on the PMC list, and hit aelfred.jar, an XML parser needed for Jalopy (in the tools directory). While the license apparently might eventually allow for inclusion in our CVS/distribution [1], we figured to question the necessity of having Jalopy in Cocoon at all.
I think programmatical enforcement (let alone agreement on the required rules) of code style isn't likely to happen, nor have we been seeing much problems with coding style differences.
Let's drop Jalopy. Your votes please.
I'm +1.
[1] please, please check licenses of new libraries and their own dependency libraries when adding new stuff to CVS!
</Steven> -- Steven Noels http://outerthought.org/ Outerthought - Open Source Java & XML An Orixo Member Read my weblog at http://blogs.cocoondev.org/stevenn/ stevenn at outerthought.org stevenn at apache.org
