You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "Justin Mclean (Jira)" <ji...@apache.org> on 2022/01/10 23:39:00 UTC

[jira] [Commented] (LEGAL-594) How do projects handle dual-licensed dependencies?

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

Justin Mclean commented on LEGAL-594:
-------------------------------------

In general where you have something dull licensed you can pick the more favourable license. This is already documented please see https://www.apache.org/legal/resolved.html#mutually-exclusive

> How do projects handle dual-licensed dependencies?
> --------------------------------------------------
>
>                 Key: LEGAL-594
>                 URL: https://issues.apache.org/jira/browse/LEGAL-594
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Christopher Tubbs
>            Priority: Major
>
> Some projects may have questions about how to include dependencies that are multiply-licensed (usually, dual-licensed).
> It would be good to document on https://www.apache.org/legal/resolved.html how such dependencies should be handled, especially if one of the licenses is in category A/B and the other is in category X.
> It seems clear to me that if a dependency is licensed under category A/B, we can include them as though they were exclusively licensed under those, and can ignore the fact that they are also available under separate terms (such as category X). However, it would good to document this on that page, so project members aren't confused about this situation.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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