Hi,
Is the TCK the last thing left? I can understand the concern there for sure. I know there is a lot of work being done with the platform TCK itself. I'm not sure how that is going.
We are part of Wave 5, but I don't know how much time that buys us
"Wave 5 specs to have release review by 2024-02-29." (see spec mailing list)
Thank you! I knew I had seen it somewhere, but was struggling to find it.
Jersey for instance hasn't even started yet with any kind of Jakarta REST 4.0 support. I'm a committer there, though admittedly not a very active one, so I didn't want to just start on it. When I started a discussion about Jersey for 4.0 this week, the first reaction I got was "Is there any rush for the 4.0 branch?", which may be quite indicative of the current situation.
I can say that the plan for RESTEasy was to start making more progress in January. The biggest hurdles will be the @Context injection stuff. I've removed what I can from the test suite and replaced it with CDI, but there is still work to be done with ContextResolvers and parameter injection. Most of that can happen without the spec itself being released. However, having a TCK would be nice.
