-
Notifications
You must be signed in to change notification settings - Fork 555
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding jakarta servlet API 6 compatibility #247
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the servlet is completely unchanged by this dependency upgrade, why bump the major version number to 3.0?
@dsmiley I had the thought that a key dependency version bump to a major number warranted a major version change as well to signal it clearly, but there is no other reason, so if it's more aligned we could just bump a minor |
Let's continue to test that the previous version works as well, since it is a key dependency. |
Added 5 and 6 to the compatibility testing matrix, tested both manually locally and tests are happy as expected. Went for a closed list of options compatibility ( Also moved back to 2.2 as versioning bump, would that be more coherent? We're leaving it open in the pom and testing with both (and the rest of combinations on the matrix), so we're basically saying that you can use this component with either of the two as a dependency. AFAIU. |
Looks like there is a format issue with the yaml, looking into it |
Having a deeper read of https://docs.github.com/en/actions/using-jobs/using-a-matrix-for-your-jobs Looks like |
I am trying to use the proxy with jetty 12 ee10, which uses jakarta 6. This change and version bump uses v6
(context https://en.wikipedia.org/wiki/Jakarta_EE).
All tests pass and package is generated