The point is that for contractual reasons, we must adhere to the specifications and what is supported by JBoss EAP 8.1 (JEE 10). We can’t use SB 4 until JBoss also supports JEE 11.
The 6.6 artifact was developed for JUnit 5.13, this doesn’t mean it couldn’t also work with 5.14, which I believe will be the last of the 5.x versions. But that’s not the point, the point is that your implementation is based on a construct that effectively constrains and blocks your libraries.
You can also just create your own version of hibernate-testing that works with newer JUnit versions, but we have decided and published that our maintenance policy demands stability, which means no backports of features or enhancements. If you are a Red Hat or IBM customer, you might be able to convince us that we should support newer JUnit versions also in such limited-maintenance branches.
This isn’t viable and isn’t acceptable, much like your policies, so I’m afraid the only option left is to abandon your testing library. We’ll definitely keep these restrictions in mind when using your library in the future.
Thanks.