forked from spring-projects/spring-framework
-
Notifications
You must be signed in to change notification settings - Fork 0
update the code #2
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
Merged
Merged
Conversation
This file contains hidden or 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
* pr/29308: Upgrade to Dokka 1.7.20 Closes gh-29308
# Conflicts: # spring-beans/src/main/java/org/springframework/beans/CachedIntrospectionResults.java # spring-beans/src/main/java/org/springframework/beans/PropertyDescriptorUtils.java # spring-beans/src/main/java/org/springframework/beans/SimpleBeanInfoFactory.java # spring-beans/src/main/java/org/springframework/beans/factory/support/AbstractBeanFactory.java
HttpServiceProxyFactory now support programmatic initialization through a builder, while bean-style initialization is deprecated. See gh-29296
Prior to this commit, AnnotationTypeMapping logged a warning for the use of convention-based annotation attribute overrides in composed Bean Validation constraint annotations, even though those attribute overrides are not related to Spring. For example, Hibernate's @url constraint annotation is meta-annotated with Bean Validation's @pattern constraint annotation, and we should not log a warning in such scenarios. This commit addresses that by not logging a warning if convention-based annotation attribute overrides are detected for a composed @constraint annotation. Closes gh-29206
* pr/29326: Add missing since on setCurrentlyInvokedFactoryMethod() Closes gh-29326
* pr/29313: Make RestTemplate.createResourceAccessException() private Closes gh-29313
Tested successfully using the following locally built GraalVM dev build. OpenJDK Runtime Environment GraalVM 22.3.0-dev (build 17.0.5+5-jvmci-22.3-b07) Closes gh-29214
… in toStringAST() Prior to this commit, ternary and Elvis expressions enclosed in parentheses (to account for operator precedence) were properly parsed and evaluated; however, the corresponding toStringAST() implementations did not enclose the results in parentheses. Consequently, the string representation of the ASTs did not reflect the original semantics of such expressions. For example, given "(4 % 2 == 0 ? 1 : 0) * 10" as the expression to parse and evaluate, the result of toStringAST() was previously "(((4 % 2) == 0) ? 1 : 0 * 10)" instead of "((((4 % 2) == 0) ? 1 : 0) * 10)", implying that 0 should be multiplied by 10 instead of multiplying the result of the ternary expression by 10. This commit addresses this by ensuring that SpEL ternary and Elvis expressions are enclosed in parentheses in toStringAST(). Closes gh-29463
- Change "you ca" to "you can" in webflux.adoc - English names can be used in "month" field instead of "day-of-month" field in cron expressions in integration.adoc Closes gh-29469
…hint.support Avoids an accidental package cycle between aot and core (only aot->core allowed). See gh-29429
Prior to this commit, it was possible to register hints for individual test classes programmatically via the org.springframework.test.context.aot.TestRuntimeHintsRegistrar SPI; however, that requires that a custom TestRuntimeHintsRegistrar be registered via "META-INF/spring/aot.factories". In addition, implementing a TestRuntimeHintsRegistrar is more cumbersome than using the core mechanisms such as @Reflective, @ImportRuntimeHints, and @RegisterReflectionForBinding. This commit address this by introducing support for @Reflective and @ImportRuntimeHints on test classes. @RegisterReflectionForBinding support is available automatically since it is an extension of the @Reflective mechanism. Closes gh-29455
Prior to this commit, the server observability support would create a cycle in Java packages. This commit refactors the current arrangement to solve this by: * "flattening" the reactive HTTP instrumentation; this removes the dependency to the `ServerWebExchange` and `PathPattern` types * moving the `observation` package under `org.springframework.http.server` and `org.springframework.http.server.reactive` See gh-29477
SocketUtils was officially deprecated in 5.3.16 (gh-28052) and removed in 6.0 M3 (gh-28054); however, there is still need for a subset of this functionality in integration tests for testing scenarios in which it is not possible for the system under test to select its own random port (or rely on the operating system to provide an ephemeral port). This commit therefore introduces a scaled down version in the spring-test module called TestSocketUtils which supports retrieval of a single TCP port. See gh-29132
# Conflicts: # spring-core/src/test/java/org/springframework/util/SocketUtilsTests.java
# Conflicts: # spring-beans/src/main/java/org/springframework/beans/factory/annotation/AutowiredAnnotationBeanPostProcessor.java
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.
No description provided.