If I remember well, you still have to
declare the old version of the protocol, but perhaps it changed.
If not, the issue is still valid. And even if it is not valid any
more (I did not use Arquillian for some 3 years) - why is it still
open? Who maintains Arquillian? Some 4 years ago I was fixing
nullpointers in Arquillian Core. At least those fixes were merged
to the current 1.7.alphas. This one is still waiting:
https://github.com/arquillian/arquillian-core/pull/448
This is also horrible. Arquillian
should have real 1.7.0 and 1.7.1 and on. There was no final
version since 2020.
But the most important thing is - the
decision should be made especially by people which would have to
maintain the TCK.
This discussion is rather about
pointing out risks, pros and cons, possible additional issues.
David.
On 30. 04. 23 22:26, Arjan Tijms wrote:
Hi,
444 must be invalid. Obviously Arquillian is compatible
with EE 10, as major parts of the TCK for EE 10 work with
Arquillian. Every released (ratified) EE version is
therefore automatically compatible with Arquillian.
Kind regards,
Arjan Tijms
could
simplify the testing process and make it more
accessible to new developers. Additionally, we aim to
create an easy-to-integrate, contribute, and
extensible TCK that can be used for both Jakarta NoSQL
and Data specifications.
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
--
David Matejcek | OmniFish
david.matejcek@xxxxxxxxxxx