You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jcp-open@apache.org by David Blevins <da...@gmail.com> on 2014/04/21 21:46:35 UTC

Re: TCKs and the ASF - Section 2.1(c)(ii)

On Apr 21, 2014, at 10:49 AM, David Blevins <da...@gmail.com> wrote:

>> 4) Section 2.1(c)(ii) requires licensees to include a notice with intermediate
>> builds, identifying them as such and requiring preservation of the notice with
>> any redistribution. This restriction is incompatible with the Apache License,
>> which only requires the preservation of attribution notices. We would have no
>> problem with including the notice without the notice-preservation requirement.

Mark Thomas said it best:

"That said, no downstream consumer is going to be able to make any
statements about JSR compatibility without passing the TCK themselves so
they would pick up the notice requirement through their own TCK license."

This one seems to take care of itself without the need for a notice-preservation requirement.

Bottom line: you need your own license to claim compliance.


-David