2.1.0 deprecations #4338
Merged
2.1.0 deprecations #4338
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jplock
approved these changes
Oct 25, 2021
|
Hey there. I came here looking for some idea when jetty would be upgraded past 9 - I for one am looking forward to the upgrade! |
|
@javajosh Jetty 10 ( Dropwizard 2.x is targeting Java 8 or higher, so Dropwizard 2.x most likely won't upgrade to Jetty 10 or later. |
|
Additionally, the upgrade seems to be impossible at the moment. There are conflicts with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since most dependencies have released 'jakarta versions' (only logback hasn't at the moment), Dropwizard 3.0.0 could be built soon. But therefore some properties have to be removed:
LocalizationMessagesfromjersey-apache-connectorseems to be used):RequestConfig.Builderdoesn't supportnormalizeURIany moreServiceUnavailableRetryStrategyandHttpRequestRetryHandlerare combined inHttpRequestRetryStrategy. Therefore deprecate usingServiceUnavailableRetryStrategyHttpProcessorcannot be provided any moreDefaultHealthFactorydefines two getter and setter methods for the propertyhealthChecks. Therefore deprecate oneThe dependency updates will probably introduce more changes, but this is what I recognized so far.