Use of cache-api-1.0.0.jar - Isn't this an incompatible license?

[Joe Witt]

Ignite Devs,

In evaluating integration with Apache Ignite we discovered a questionable jar 'cache-api-1.0.0.jar'.  There are threads which clearly indicate it is known that this library uses a non ASF and ASLv2 licensing friendly license.  That jar is licensed under here

   https://raw.githubusercontent.com/jsr107/jsr107spec/master/LICENSE.txt

You even have binary convenience bundles which include it and you point to it here in your NOTICE file
   
   https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=assembly/LICENSE_FABRIC;hb=de8684390cb2c5664f4bb8401f4169e930a07e10

There are also threads where it is discussed just how problematic it is both at the JSR level and by the Ignite community.

   https://github.com/jsr107/jsr107spec/issues/333
    http://apache-ignite-users.70518.x6.nabble.com/ignite-cache-api-licensing-issue-td3306.html

I don't see a JIRA to resolve this in Ignite or in Apache Legal.  So can you help me understand if I am missing an important detail or exemption?

Thanks
Joe

[dsetrakyan]

There is a ticket to switch to the geronimo jar for Ignite 2.0:
https://issues.apache.org/jira/browse/IGNITE-2949

In general, you can just replace the jcache jar with the geronimo jcache
jar in the mean time.

We could not replace it in the recent 1.7 release because of some
serialization issues within already running clusters. However, if you are
starting out, you should be OK with the geronimo jcache jar as it is fully
compatible from API standpoint.

D.

On Thu, Aug 25, 2016 at 8:47 AM, Joe Witt <[hidden email]> wrote:

> Ignite Devs,
>
> In evaluating integration with Apache Ignite we discovered a questionable
> jar 'cache-api-1.0.0.jar'.  There are threads which clearly indicate it is
> known that this library uses a non ASF and ASLv2 licensing friendly
> license.  That jar is licensed under here
>
>    https://raw.githubusercontent.com/jsr107/jsr107spec/master/LICENSE.txt
>
> You even have binary convenience bundles which include it and you point to
> it here in your NOTICE file
>
>    https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> plain;f=assembly/LICENSE_FABRIC;hb=de8684390cb2c5664f4bb8401f4169
> e930a07e10
>
> There are also threads where it is discussed just how problematic it is
> both at the JSR level and by the Ignite community.
>
>    https://github.com/jsr107/jsr107spec/issues/333
>     http://apache-ignite-users.70518.x6.nabble.com/ignite-
> cache-api-licensing-issue-td3306.html
>
> I don't see a JIRA to resolve this in Ignite or in Apache Legal.  So can
> you help me understand if I am missing an important detail or exemption?
>
> Thanks
> Joe
>

[Joe Witt]

Thanks for your reply.  It is interesting that there is a clean implementation of that API available but glad to hear it.  We'll complete the APache NiFi integration with Apache Ignite once that jar gets incorporated in an official release.  Thanks

On 2016-08-25 13:21 (-0400), Dmitriy Setrakyan <[hidden email]> wrote:

> There is a ticket to switch to the geronimo jar for Ignite 2.0:
> https://issues.apache.org/jira/browse/IGNITE-2949
>
> In general, you can just replace the jcache jar with the geronimo jcache
> jar in the mean time.
>
> We could not replace it in the recent 1.7 release because of some
> serialization issues within already running clusters. However, if you are
> starting out, you should be OK with the geronimo jcache jar as it is fully
> compatible from API standpoint.
>
> D.
>
> On Thu, Aug 25, 2016 at 8:47 AM, Joe Witt <[hidden email]> wrote:
>
> > Ignite Devs,
> >
> > In evaluating integration with Apache Ignite we discovered a questionable
> > jar 'cache-api-1.0.0.jar'.  There are threads which clearly indicate it is
> > known that this library uses a non ASF and ASLv2 licensing friendly
> > license.  That jar is licensed under here
> >
> >    https://raw.githubusercontent.com/jsr107/jsr107spec/master/LICENSE.txt
> >
> > You even have binary convenience bundles which include it and you point to
> > it here in your NOTICE file
> >
> >    https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > plain;f=assembly/LICENSE_FABRIC;hb=de8684390cb2c5664f4bb8401f4169
> > e930a07e10
> >
> > There are also threads where it is discussed just how problematic it is
> > both at the JSR level and by the Ignite community.
> >
> >    https://github.com/jsr107/jsr107spec/issues/333
> >     http://apache-ignite-users.70518.x6.nabble.com/ignite-
> > cache-api-licensing-issue-td3306.html
> >
> > I don't see a JIRA to resolve this in Ignite or in Apache Legal.  So can
> > you help me understand if I am missing an important detail or exemption?
> >
> > Thanks
> > Joe
> >
>

[dsetrakyan]

On Thu, Aug 25, 2016 at 11:06 AM, Joe Witt <[hidden email]> wrote:

> Thanks for your reply.  It is interesting that there is a clean
> implementation of that API available but glad to hear it.  We'll complete
> the APache NiFi integration with Apache Ignite once that jar gets
> incorporated in an official release.  Thanks
>

Sounds good. Ignite 2.0 will likely be out in November.

>
> On 2016-08-25 13:21 (-0400), Dmitriy Setrakyan <[hidden email]>
> wrote:
> > There is a ticket to switch to the geronimo jar for Ignite 2.0:
> > https://issues.apache.org/jira/browse/IGNITE-2949
> >
> > In general, you can just replace the jcache jar with the geronimo jcache
> > jar in the mean time.
> >
> > We could not replace it in the recent 1.7 release because of some
> > serialization issues within already running clusters. However, if you are
> > starting out, you should be OK with the geronimo jcache jar as it is
> fully
> > compatible from API standpoint.
> >
> > D.
> >
> > On Thu, Aug 25, 2016 at 8:47 AM, Joe Witt <[hidden email]> wrote:
> >
> > > Ignite Devs,
> > >
> > > In evaluating integration with Apache Ignite we discovered a
> questionable
> > > jar 'cache-api-1.0.0.jar'.  There are threads which clearly indicate
> it is
> > > known that this library uses a non ASF and ASLv2 licensing friendly
> > > license.  That jar is licensed under here
> > >
> > >    https://raw.githubusercontent.com/jsr107/jsr107spec/master/
> LICENSE.txt
> > >
> > > You even have binary convenience bundles which include it and you
> point to
> > > it here in your NOTICE file
> > >
> > >    https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > > plain;f=assembly/LICENSE_FABRIC;hb=de8684390cb2c5664f4bb8401f4169
> > > e930a07e10
> > >
> > > There are also threads where it is discussed just how problematic it is
> > > both at the JSR level and by the Ignite community.
> > >
> > >    https://github.com/jsr107/jsr107spec/issues/333
> > >     http://apache-ignite-users.70518.x6.nabble.com/ignite-
> > > cache-api-licensing-issue-td3306.html
> > >
> > > I don't see a JIRA to resolve this in Ignite or in Apache Legal.  So
> can
> > > you help me understand if I am missing an important detail or
> exemption?
> > >
> > > Thanks
> > > Joe
> > >
> >
>