You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "Herve Boutemy (Jira)" <ji...@apache.org> on 2021/12/04 17:38:00 UTC
[jira] [Commented] (LEGAL-586) Include C header file licensed under GPLv2 w/CPE
[ https://issues.apache.org/jira/browse/LEGAL-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453462#comment-17453462 ]
Herve Boutemy commented on LEGAL-586:
-------------------------------------
to me, Guillaume's commit fixes the issue: https://github.com/mvndaemon/mvnd/commit/47b4b111a69197f8e6c7de818a90a15a19a2982b
> Include C header file licensed under GPLv2 w/CPE
> ------------------------------------------------
>
> Key: LEGAL-586
> URL: https://issues.apache.org/jira/browse/LEGAL-586
> Project: Legal Discuss
> Issue Type: Question
> Reporter: Guillaume Nodet
> Priority: Major
>
> We're going through the IP clearance process to include mvnd [1] in the Maven project.
> It happens that mvnd is including native code (C) for Java and currently includes a bunch of C header files from Oracle [2]. The versions that are in use in the source tree are quite old but they could be replaced with more recent ones that are licensed under GPLv2 w/CPE such as [3]. Would that be acceptable in the source tree of an Apache project ?
> [1] https://github.com/mvndaemon/mvnd
> [2] https://github.com/mvndaemon/mvnd/tree/master/native/src/main/native/inc_linux
> [3] https://github.com/openjdk/jdk/blob/master/src/java.base/share/native/include/jni.h
--
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