-
Notifications
You must be signed in to change notification settings - Fork 38.9k
Modernize java.time API usages
#35861
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
base: main
Are you sure you want to change the base?
Conversation
...src/main/java/org/springframework/context/aot/ReflectiveProcessorAotContributionBuilder.java
Outdated
Show resolved
Hide resolved
spring-web/src/main/java/org/springframework/http/server/DefaultPathContainer.java
Outdated
Show resolved
Hide resolved
mdeinum
left a comment
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.
Looking at existing rules and deliberate care in dependencies I would expect some changes. Which would mean that the rewrite rules aren't applicable.
StreamRulesRecipesTimeRulesRecipes
a8e5b97 to
def2188
Compare
Thank you for the kind feedback. I’ve reworked the scope to focus on the TimeRules. Hopefully this is something easier to consider.
I think it’s difficult to judge something universally or generically; each scope has its own individual context. This is the first project that passed the included GradleBestPractices checks without any findings. Considering the Java8toJava11 migration, as explored in
the code compiles on Java 21+ while still largely using Java 8–era and Java 17–era constructs. |
spring-test/src/main/java/org/springframework/test/http/HttpHeadersAssert.java
Show resolved
Hide resolved
spring-test/src/test/java/org/springframework/test/web/servlet/client/RestTestClientTests.java
Show resolved
Hide resolved
| @Test | ||
| void resolveCustomizedAndTimeZoneLocale() { | ||
| TimeZone timeZone = TimeZone.getTimeZone(ZoneId.of("UTC")); | ||
| TimeZone timeZone = TimeZone.getTimeZone(ZoneOffset.UTC); |
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.
this seems a good thing to consider, being straight up instead of "error prone".
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.
What do you mean?
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.
sorry i meant this is a good thing and seems easy consider suggest, as it avoids error prone (random) string.
...rg/springframework/web/servlet/mvc/method/annotation/HttpEntityMethodProcessorMockTests.java
Show resolved
Hide resolved
|
We prefer to not introduce new tooling infrastructure in our build, please refine this PR to only include the |
|
yes of course, thanks for the kind feedback. |
Signed-off-by: Vincent Potucek <[email protected]>
f3e25e5 to
d87c456
Compare
rickie
left a comment
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.
Looks good! Thanks for applying @Pankraz76
I’d kindly like to suggest considering Error Prone integration featuring the TimeRules findings:
As discussed in:
rewritesupport forerrorprone.refasterrules#35270PS:
Congratulations on the recent major release — a lot of work has clearly gone into it.
I'm sure Spring Boot will continue to succeed as well.