3 ms·
They own the trademark, they own the TCK and Java itself is a huge amount of tech, not something easy to fork. Plus it would be really hard to get adoption for
by oblio 8y ago
They own the trademark, they own the TCK and Java itself is a huge amount of tech, not something easy to fork.
Plus it would be really hard to get adoption for the fork. The Java brand is huge and many of its users are late adopters or even laggards.
- kjeetgill 8y agoThe TCK was recently open sourced!
- oblio 8y agoOh, interesting. Didn't know that.
- kodablah 8y agoLink? Surely we're talking about the regular TCK to confirm my Java impl is compliant and not EE.
- alanfranzoni 8y agohttps://github.com/eclipse-ee4j/jakartaee-tck/blob/master/README.md https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/RE...
- kodablah 8y agoThat's EE. Not the TCK that people have complained about their subjective licensing of (e.g. Apache Harmony). When they really open the TCK, that would be nice. In the meantime, this is just for EE stuff of which licensing matters little these days.