> Why did you give up? > I'm unable to enumerate number of bugs we solved, or even dropped as unsolvable due to dynamic nature of distribution-correct JDK. > > At one point AdoptOpenJDK distributed binaries that were not tested > against the TCK (https://dzone.com/articles/an-overview-on-jdk-vendors). They indeed did it once, and had pretty hard time fromthat. Now they TCK propelry. > > Why is running the TCK such a burden? Is it due to hardware > resource limitations? Do we really need to claim that > we are Java SE compatible? We ahve claim the comaptibility. Tck run in the paralel mode 24h per os and arch and jdk. And there are tricky issues, and even more tricky failures. So both human and hw cycles are heavily under preassure > > > Is this purely because of the TCK requirement? If so, I would prefer > that Fedora ship an uncertified binary, or ship both a certified > static binary and an uncertified dynamic binary, with the latter > being the default. Interesting idea. Not sure if legally possible but worthy of shot. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
