jcache-api license issue

[Jens Wilke]

Hi Greg, Hi Brain,

I think that jcache-api is not distributed with an OS license is the most critical
issue we have right now.

RI and TCK is released under Apache, but this licensing is actually invalid since they
depend on the jcache-api which has currently not a OS license.

Can you please update the issue:
https://github.com/jsr107/jsr107spec/issues/333

Questions:
- Can we fix this ASAP and release JCache under Apache?
- Is this a longer process involving legal department?
- If we cannot release JCache under Apache, then the RI and TCK licenses need to change also as well
as any other OS project. What are the plans?

Best,

Jens

--
"Everything superfluous is wrong!"

// Jens Wilke - headissue GmbH - Germany
\// https://headissue.com

[Werner Keil]

Judging from our experience at JSR 363 which Eclipse SmartHome has a strong desire to use (and at least a dozen other Eclipse and similar projects which now use JSR 275 in production completely at their own risk;-) this sounds like a good idea.

Eclipse Orbit and similar Open Source ecosystems cannot deal with the Spec License, therefore we use the RI/TCK license (BSD 3-clause in our case) for "all Software Artifacts" (including the public API) now. 

Given many of the newer JSRs also do, including the likes of 375 (Oracle-led) or MVC 1.0, I suggest the next major upgrade of JCache, either a MR or 2.x does the same.

Werner