You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "Henri Yandell (JIRA)" <ji...@apache.org> on 2017/01/16 04:50:27 UTC

[jira] [Commented] (LEGAL-280) Can java based projects broadly have optional modules with Cat X dependencies?

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

Henri Yandell commented on LEGAL-280:
-------------------------------------

I believe that's the intent of:

http://www.apache.org/legal/resolved.html#optional

Perhaps the solution is to reword that and http://www.apache.org/legal/resolved.html#prohibited so that the questions are the simpler:

"Can Apache projects distribute components under prohibited licenses?"  (the current #prohibited answer of 'No')
"Can Apache projects rely on components under prohibited licenses?"  (the current #optional answer)

> Can java based projects broadly have optional modules with Cat X dependencies?
> ------------------------------------------------------------------------------
>
>                 Key: LEGAL-280
>                 URL: https://issues.apache.org/jira/browse/LEGAL-280
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: John D. Ament
>
> This is a follow up to https://issues.apache.org/jira/browse/LEGAL-198 where we introduce that Amazon License is OK if its an optional dependency.
> Does this apply to anything in Cat-X or specifically to those under field of use restrictions or specifically to the Amazon License?
> This probably is limited to java/jvm projects, where its an optional feature (e.g. the library still works without it or has an alternative that can be dropped in instead) that is included in a convenience binary.  To build the optional module from source, you would need to have the LGPL library available locally in binary form (I would imagine).
> - Java projects like this are not directly distributing the LGPL dependency
> - They may use build tools, or provide other such means, to download these software (e.g. its clear to the user)
> - Its dynamically linked, by definition.  E.g. we wouldn't produce an "uber jar" or anything that in some way bundled the extra dependency in a way that was non-obvious to the user
> - I'm assuming this precludes modifications to the 3rd party library, since those couldn't be licensed under ALv2



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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