> As far as L/GPL jars go that's not something Maven controls. Projects
> state their own dependencies and if an Apache project is violating
> Apache policies how is that Maven's problem? If it was an Ant build that
> used the <get/> task to link in an L/GPL jar is that Ant's problem?
> Obviously not.
So, assuming[1] for the moment that LGPL jars can not be imported into
ASF code:
Can we agree that
1. It is not allowed for Maven or any of its plugins which are
licensed to import (L)GPL code
2. Plugins distributed under a different license and distributed
from a non ASF location could have such dependencies without
creating difficulties for the ASF. For example, a checkstyle
plugin with the same license as checkstyle and hosted at
sourceforgot. (For any who do not know, plugin installation and
resolution in maven is a completely runtime activity)
3. Projects which use Maven can explicately declare a dependency of
(L)GPL code and maven can download the dependency artifacts and
build the project without causing difficulty for the ASF. (Maven
should be able to build projects which are themselves GPL right?
Ant certainly can).
Thanks,
James
.. [1]: Hopefully I am not the only person who disagrees with this
decision, but I understand if the ASF is not willing to take a legal
stand on the import == #include issue.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
