|
|
|
|
|
by henk53
4064 days ago
|
|
The matter at hand here was pull requests and the implied notion that those didn't happen in the Java EE universe, which I proved (again) was not true. Instead of just acknowledging that in whatever way you're just evading the issue (again) and switching to another topic. But to reply this new topic, TCK has been a thorn in the JCP process indeed. Not every spec has a closed TCK. CDI and Bean Validation have open ones, based on Arquillian, with an open source (OSI) license, and an associated issue tracker where everyone can open issues against it. Now funny thing here is that CDI is rapidly becoming the underpinning of everything in Java EE. It's the core of Java EE's core. For some other specs like JSF the TCK is unfortunately closed, but the RI (Mojarra) has such an extensive set of effective TCK tests that I wonder if there's anything at all in the TCK that's not covered by the RI tests. Still, opening up the TCKs is another battle worth fighting. |
|