Sounds like trouble to me. Thanks for bringing this up! Andrey
> Date: Wed, 2 Mar 2016 10:53:24 -0800 > From: [email protected] > To: [email protected] > Subject: RE: ignite cache-api licensing issue > > Can't say I'm a license expert but it was pointed out by my legal department. > Here is my understanding of the issue: Anyone who would like to use > apache-ignite is now forced to accept the license of cache-api-1.0.0.jar. > That license pretty much does not permit the use of the cache-api beyond the > evaluation or implementation purposes. Hence apache-ignite or any other > implementations with the runtime dependency on cache-api-1.0.0.jar can not > be used beyond the evaluation. Here is a link to more details from the > issue raised in jsr107 space: > https://github.com/jsr107/jsr107spec/issues/333 . Based on this discussion > the options seems to be either to change cache-api-1.0.0.jar licensing to > Apache 2.0 (hopefully this is possible) or change apache-ignite to use > geronimo-jcache_1.0_spec which is apache JCache API. > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/ignite-cache-api-licensing-issue-tp3306p3344.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
