3 ms·
It should be noted that AdoptOpenJDK does not run the TCK against these binaries so they can not be called a compatible Java implementation.
by needusername 7y ago
It should be noted that AdoptOpenJDK does not run the TCK against these binaries so they can not be called a compatible Java implementation.
- bad_user 7y agoThe TCK is not open, it isn't governed by a standards body, the TCL is completely in Oracle's control. If Java is to evolve as an open platform, it needs to break free from the TCK that disallowed Apache Harmony to exist. We don't need it and an independent TCK could be developed.
- needusername 7y agoYet any other OpenJDK distribution from Alibaba, Amazon, Azul, BellSoft, RedHat, SAP (I probably forgot some) all run the TCK. All except AdoptOpenJDK. And whenever you bring that up the only response is ranting about the TCK.
- bad_user 7y agoAll the companies you mentioned have backroom commercial agreements with Oracle, which is why they are allowed to run the TCK. The existence and reliance on that TCK however means that Java is NOT an open platform, not as long as you insist on having implementations pass the TCK, compliance that's defined by whatever Oracle wants. And lets be clear about this, we are talking about what Oracle wants, not about JCP, which btw is only a farce of a standards body, not a real one. This problem is old and I invite people to not be ignorant about the issue at play. Please read Apache's open letter to the former Sun Microsystems, as it does justice to this issue better than I could: https://www.apache.org/jcp/sunopenletter.html https://www.apache.org/jcp/sunopenletter.html --- The irony of the situation is that the direct competition, .NET and C#, are managed by a real standards body and alternative open source implementations (e.g. Mono) have been allowed to exist, without backroom deals with Microsoft ;-)
- karianna 7y agoNo ranting from us :-). We've not been granted access to the TCK and we continue to hold an open dialogue with Oracle on this. We hope to get this resolved down the line!