[
https://issues.apache.org/jira/browse/LUCENE-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463329#comment-13463329
]
Uwe Schindler commented on LUCENE-4431:
---------------------------------------
>From the Apache License Docs:
{quote}
Each license in this category requires some degree of reciprocity; therefore,
additional action must be taken in order to minimize the chance that a user of
an Apache product will create a derivative work of a reciprocally-licensed
portion of an Apache product without being aware of the applicable requirements.
The first action that must be taken is that software under the following
licenses may only be included in within an Apache product if the inclusion is
appropriately labeled:
- CDDL 1.0
- ...
For small amounts of source that is directly consumed by the ASF product at
runtime in source form, and for which that source is unlikely to be changed
anyway (say, by virtue of being specified by a standard), this action is
sufficient. An example of this is the web-facesconfig_1_0.dtd, whose inclusion
is mandated by the JSR 127: JavaServer Faces specification.
Code that is more substantial, more volatile, or not directly consumed at
runtime in source form may only be distributed in binary form.
By including only the object/binary form, there is less exposed surface area of
the third-party work from which a work might be derived; this addresses the
second guiding principle of this policy. By attaching a prominent label to the
distribution and requiring an explicit action by the user to get the
reciprocally-licensed source, users are less likely to be unaware of
restrictions significantly different from those of the Apache License; this
addresses the fourth guiding principle of this policy.
Although the source must not be included in Apache products, the NOTICE file,
which is required to be included in each ASF distribution, must point to the
source form of the included binary (more on that in the forthcoming "Receiving
and Releasing Contributions" document).
Note that works written in a scripting language without a binary form cannot be
included in any ASF product under one of these licenses (see Transition and
Exceptions). In addition, C-based projects may have difficulty using works
under these licenses since they would have to deal with platform-specific
binaries, rather than just distributing source that can be built on most any
platform.
{quote}
In fact our use is exactly like described there: We dont ship with this file at
all (its nowhere in any ZIP/TGZ) and so no derivative work can be created.
> License of servlet-api.jar is NOT ASF, it is CDDL! We must fix and add
> NOTICE.txt
> ---------------------------------------------------------------------------------
>
> Key: LUCENE-4431
> URL: https://issues.apache.org/jira/browse/LUCENE-4431
> Project: Lucene - Core
> Issue Type: Bug
> Components: modules/other
> Affects Versions: 4.0-BETA
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Priority: Blocker
> Fix For: 4.1, 5.0, 4.0
>
> Attachments: LUCENE-4431.patch
>
>
> - The demo module has sevlet-api.jar with a ASF-named license file and the
> text "TODO: fill in"
> - This also affects Solr: It has a full ASF license file, but that is wrong.
> The servlet-apoi file is CDDL license:
> http://download.oracle.com/otndocs/jcp/servlet-3.0-fr-eval-oth-JSpec/ (same
> for 2.4). The 3.0.1 JAR file also contains License in its META-INF folder.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
