Steven,The issue was with the perception that it was GPL. In fact, from that page, I can see that there is a GPL version, but that the Saxon version is in fact issued on a BSD style licence, and is thus okay. Depending upon which version of Aelfred we have in CVS, this licence issue might be a red-herring. Anyway, perhaps removing Jalopy is a good thing anyway.
Please can you give more details of what the license problem is? Saxon also
uses aelfred.jar also - see http://saxon.sourceforge.net/aelfred.html
Regards, Upayavira
thanks,
Mark Butler
Research Scientist HP Labs Bristol
http://www-uk.hpl.hp.com/people/marbut
-----Original Message-----
From: Steven Noels [mailto:[EMAIL PROTECTED] Sent: 17 February 2004 14:44
To: [EMAIL PROTECTED]
Subject: [vote] Removing Jalopy
Hi all,
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>
