www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LEGAL-206) "greenmail" library purported to be ASL may actually be LGPL; is a dependency in several ASF projects
Date Sun, 06 Jul 2014 21:30:33 GMT

    [ https://issues.apache.org/jira/browse/LEGAL-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053231#comment-14053231
] 

Hoss Man commented on LEGAL-206:
--------------------------------

bq. I don't know what you've been told. If you can point to specific documentation that implies
otherwise, we can work on fixing...

Literally the first example i found when searching the mail archives for LGPL...

https://mail-archives.apache.org/mod_mbox/www-legal-discuss/200801.mbox/%3C3d4032300801220524v58d8b261r23d3c40feae3db33@mail.gmail.com%3E

{noformat}
> Yes.  The functionality that depends on RXTX is completely optional.
>
> > 2) Does this submodule "communicate with RXTX solely through the Sun
> > Microsytems [sice] CommAPI interface version 2"?
>
> No, it directly imports gnu.* package.

What a pity, as this would have changed the answer.  But given the
answers above, the answers to your two questions relative to the
current draft ASF Third Party Licensing policy is

> > > 1) Do we need to move our submodule outside of the ASF or not?

Yes.
{noformat}

...even though it's an optional module, because it compiles directly against the LGPL API,
it's not allowed.

----

Or for example, this guidance regarding maven and pulling in LGPL dependencies...

https://mail-archives.apache.org/mod_mbox/www-legal-discuss/200801.mbox/%3C200801250935.54242.dkulp@apache.org%3E

...which seems to make it clear, that builds can't automatically compile download an LGPL
jar, it has to be something non-standard via a "profile" the person compiling explicitly chooses.


----

There is also the fact that LEGAL-192 is still open -- if the issue was as cut & dry as
you describe, then why is LEGAL-192 still unresolved?



> "greenmail" library purported to be ASL may actually be LGPL; is a dependency in several
ASF projects
> -----------------------------------------------------------------------------------------------------
>
>                 Key: LEGAL-206
>                 URL: https://issues.apache.org/jira/browse/LEGAL-206
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Hoss Man
>
> Be advised that at least 5 Apache projects appear to depend on a third party library
known as "greenmail" which advertises itself in may places as being licensed under the ASL
2.0, however most of the greemail source files contain headers claiming LGPL.
> This issue requests that the Legal VP advise the affected projects on what they need
to do (if anything) moving forward to be in compliance with ASF policy.
> Projects known to be affected (but there may be more)...
> * Apache Syncope: http://svn.apache.org/repos/asf/syncope/trunk/pom.xml
> * Apache Geronimo: https://svn.apache.org/repos/asf/geronimo/javamail/trunk/geronimo-javamail_1.4/geronimo-javamail_1.4_provider/pom.xml
> * Apache OODT: http://svn.apache.org/repos/asf/oodt/trunk/protocol/imaps/pom.xml
> * Apache Oozie: https://git-wip-us.apache.org/repos/asf?p=oozie.git;a=blob;f=pom.xml;h=bad1e0fbee619f2e5020733792c4a09256b69dcf;hb=master
> * Apache Axis2: http://svn.apache.org/repos/asf/axis/axis2/java/core/trunk/modules/transport/mail/pom.xml



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Mime
View raw message