Hi all,
I've just updated the setup mentioned below to do handle the licensing issue just a tiny bit better, up to the point
where I think (IANAL!) it is no longer in violation of any license.
http://cvs.apache.org/viewcvs.cgi/avalon/check-targets.ent http://cvs.apache.org/viewcvs.cgi/avalon/check-targets.properties
It might make sense for other projects that are also not moving to maven or centipede just yet to put in place
a similar setup.
cheers,
- Leo
What is more or less clear at this point is that the current setup I just put in place for avalon-framework where some Sun BCL code is downloaded from ibiblio is in breach of license (it won't work anymore either, as the problematic jars have been removed, so I guess it is already no longer in breach), whereas the setup we use in logkit (where the user must actively agree to the BCL license and download the code themselves) /seems/ to be acceptable.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
