Replies: 1 comment 4 replies
-
After fixing the WireMock issues in #4439, the current blocker is the required Jetty upgrade to version 10 (ref. #4252). Upgrading Jetty in our codebase seems trivial to do, but Solr is also using Jetty, triggering a chain of upgrades. I've created #4441 for now, but after the comment from @barthanssens I wonder if there is another way of approaching this "knot"? WDYT about removing all Jetty dependencies from our codebase and migrating to JUnit Server fueled by Tomcat? Ref. #4437 (POC PR using Jetty underneath, but JUnit Server also supports Tomcat). Or do you see another way of approaching this? @abrokenjester @hmottestad |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As an intermediate step towards migrating from Java EE to Jakarta EE, I suggest starting with an upgrade to Jakarta EE 8 - which is supposed to be fully compatible with Java EE 8. This is the initial Jakarta EE release - before the troublesome javax->jakarta namespace change.
I have created a WIP PR for this, #4397, and it seems like the current blocker is WireMock - where a release supporting Java/Jakarta EE 8 does not exists, and there are no plans to fix this, ref. wiremock/wiremock#1967.
I have created an issue, based on a comment from @abrokenjester, #4431, and hope to get some consensus on the direction forward from the maintainers. 😃
Beta Was this translation helpful? Give feedback.
All reactions