Jetty 12 Upgrade #4310
Closed
stevenschlansker
started this conversation in
General
Replies: 1 comment 10 replies
-
@stevenschlansker I definitely don't want to add a jetty-12 module. I think we did that too much in the past and IMO it becomes unwieldy. TBH my preferred approach would be to pull it out of the resteasy project and place it in it's own project. The reason is I don't know when I'd do a new minor. That said, we could make 7.0.0 use Jetty 12. My personal option would be to deprecate it in the resteasy project though and create a new resteasy-jetty project with it's own release cycle. |
Beta Was this translation helpful? Give feedback.
10 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@jamezp , we are looking to upgrade to Jetty 12. Right now resteasy jetty client supports Jetty 11, which has reached "End Of Community Support" (not quite yet end of support, but soon)
The simplest path is to just update to Jetty 12 at some convenient resteasy minor version. I don't know how many resteasy-client-jetty users are out there, but this would be a breaking change for them.
Another option is to copy the whole client library as is to a -jetty12 artifact, fix it up, and deprecate the existing on.
If we want to support multiple Jetty versions at once, I could try to pull apart an abstract superclass - additional complexity, but easier to change Jetty versions.
How would the resteasy project want to approach a Jetty 12 transition? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions