I think you might be over-thinking this. By your interpretation, we can't distribute the tapestry-hibernate module source because of its high degree of dependence on a 3rd party LGPL-licensed software. But then we *could* distribute that same code if we moved it into Tapestry-core (because Tapestry-core *doesn't* have a high degree of dependence on Hibernate. That strikes me as bizarre.
I'd bet lots of other Apache projects are distributing such integration modules and not losing sleep over it. On Sep 27, 2012 5:25 AM, Ulrich Stärk <[email protected]> wrote: > Folks, > > I just reviewed the ASFs policy on including/linkting to software with > incompatible licenses (e.g. GPL/LGPL) [1]. If my reading is right, we are > OK to do that as long as the components depending on incompatible stuff > are not part of our official distribution. So a binary tapestry-hibernate > jar is OK since the binaries are not part of our official distribution, > only the source is. This means however, that we are not allowed to include > sources for modules that depend on software with incompatible licenses in > our official distribution, which we are currently doing, e.g. with > tapestry-hibernate. > > What we need to do is > > 1. check the licenses of all dependencies and see if they are incompatible > to the ASL > 2. remove the affected modules from the source distribution and replace > them with instructions on how to obtain them > > Uli > > [1] http://www.apache.org/legal/resolved.html#optional > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
