Enrico,
Great work. I suggest the same.
While JSR 107 does not provide a working out of the box template for running the TCK like we did with JSRs 354 or 363, this document should help:
As a caveat, I have no idea, what the license terms in the JSR 107 TCK guide means for your implementation:
>Copyright 2013 Greg Luck
>Copyright © 2013 Oracle and//or its affiliates.
>
>All rights reserved.
>
>ORACLE AMERICA, INC. HEREBY GRANTS A NON-EXCLUSIVE, NON-TRANSFERABLE, ....
It's clearly not a recognized Open Source License.
Nor is the TCK clearly licensed either.
is very obvious about a commercial proprietary Oracle TCK license (for everything other than academic or research use)
while Terracotta was never a Spec Lead of JSR 107.
One Spec Lead (Greg Luck) insists it's Apache, while at Oracle, you may ask 2 lawyers and get at least 3 different answers. Just look at the Android lawsuit on this...
So unless you have a good legal team behind you to help you interpret the actual TCK license terms you have to expect.
The good thing is, even the corporate TCK license in this case asks
A. For Commercial Licensees: fee of $0 per annum.
(unlike many other TCKs before it;-)
So it may be less severe but I still recommend you ask both ALL Spec Leads of JSR 107, not just one and get legal advise.
If applying the TCK guide the right way it would be cool if you could provide a transparent TCK test result page similar to
or
Both run the TCK against multiple implementations or platforms (e.g. Java 7 vs. 8) and everyone can see whether any tests failed or not.
Good Luck,
Werner Keil | JCP Executive Committee Member, JSR 363 Co Spec Lead | Eclipse UOMo Lead, Babel Language Champion | Apache Committer
Twitter @wernerkeil | @UnitAPI | @JSR354 | @AgoravaProj | @DeviceMap | #DevOps | #EclipseUOMo