On Mon, Mar 31, 2014 at 8:31 AM, sebb <seb...@gmail.com> wrote:
>> The jar files are also distributions and must therefore have embedded
>>> NOTICE and LICENSE files, e.g. in the META-INF directory.
>>
>> Does this warrant a new RC ?
>
> Yes, in my opinion.
Though the ASF only releases source code and the binaries are the
responsibility of the party which supplies them, I think that failing to
propagate the contents of the NOTICE file (either from the Tez source release
or from any ALv2 dependencies which may supply NOTICE files) is technically a
violation of the ALv2 section 4d. Failing to supply the license itself in
META-INF I think violates 4a.
http://www.apache.org/licenses/LICENSE-2.0.html#redistribution
a. You must give any other recipients of the Work or Derivative Works a
copy of this License; and
[...]
d. If the Work includes a "NOTICE" text file as part of its distribution,
then any Derivative Works that You distribute must include a readable
copy of the attribution notices contained within such NOTICE file,
excluding those notices that do not pertain to any part of the
Derivative Works, in at least one of the following places: within a
NOTICE text file distributed as part of the Derivative Works; within
the Source form or documentation, if provided along with the
Derivative Works; or, within a display generated by the Derivative
Works, if and wherever such third-party notices normally appear. [...]
The "wherever such third party notices normally appear" for jar files would be
META-INF.
IANAL but it seems good for the party supplying the binaries to get this
right.
Marvin Humphrey
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
