Bump spring-native.version from 0.10.1 to 0.11.0

[dependabot]

Bumps spring-native.version from 0.10.1 to 0.11.0.
Updates spring-native from 0.10.1 to 0.11.0

Release notes

Sourced from spring-native's releases.

0.11.0

Upgrading from Spring Native 0.10

• GraalVM 21.3, Spring Boot 2.6 and Spring Cloud 2021.0 should be used as baselines.
• Java 8 is not supported anymore on GraalVM side, so it is not supported anymore on Spring Native side as well. But you will likely be able to compile most Java 8 applications with the Java 11 flavor of GraalVM.
• Please read the updated AOT engine documentation to understand how it behaves.
• Less hints are now required, for example those with import selector or condition trigger should be updated to use other ones.
• Hints with a trigger are now taken in account if the specified class is reachable by GraalVM static analysis, not just with a classpath check, except for annotations where the classpath check is still used.
• Native Build Tools configuration has evolved since the version used in now 0.9.8.
• Maven plugin now requires <extensions>true</extensions> and a dependency on org.junit.platform:unit-platform-launcher, see this documentation for more details.
• Gradle plugin is now automatically imported and configured when using the AOT plugin, so by default no need for additional configuration anymore.
• AccessBits is now deprecated and TypeAccess[] is used instead to specify @TypeHint access.
• NativeConfiguration SPI has been reworked to not use anymore the now deprecated TypeSystem.
• Extension points are now using META-INF/spring.factories instead of service loader to be discovered.
• ComponentProcessor extension point has been removed and should be replaced by BeanFactoryNativeConfigurationProcessor or BeanNativeConfigurationProcessor.
• Spring libraries using child application context (like Spring Cloud LoadBalancer) are not supported yet with the new AOT engine.
• Spring Cloud Bootstrap is no longer supported.
• FunctionalSpringApplication is no longer supported.
• While building a project that contains Spring Cloud Config Client, it is necessary to make sure that the configuration data source that it connects to (such as, Spring Cloud Config Server, Consul, Zookeeper, Vault, etc.) is available. For example, if you retrieve configuration data from Spring Cloud Config Server, make sure you have its instance running and available at the port indicated in the Config Client setup. This is necessary because the application context is being optimized at build time and requires the target environment to be resolved.
• Spring Cloud Function reflection configuration is now inferred so related hints can be removed.
• Spring AOT is now a forked process, in order to debug it, follow related documentation.

Changelog

In addition to the 0.11.0 changelog below, make sure to check 0.11.0-M1, 0.11.0-M2 and 0.11.0-RC1 ones to get a complete overview of the changes since Spring Native 0.10.

⭐ New Features

• Provide implementation of BeanFactoryNativeConfigurationProcessor for function types #1351
• Provide an SPI to exclude a bean definition to be written #1349
• Avoid creating reflection entries for java and primitive types. #1346
• Do not apply AOT plugin on POM projects #1344
• Use Flag renamed to TypeAccess instead of AccessBits in @TypeHint #1317
• Add logging to BeanDefinitionRegistrar #1306
• Use NativeConfigurationRegistry in NativeConfiguration #1279
• Add support for non Spring Boot tests #1170
• Restore Spring Integration support #1134
• Add support for Spring Data MongoDB (lazy loading) DocumentReference annotation. #875

⭐ Compatibility

• Register reflection configuration for JPA AttributeConverter implementations #1347
• Method signature types for methods of javax.persistence.AttributeConverter no longer included in configuration. #1329
• Regression on OAuth2 client and resource server with WebFlux #1291
• RestController with Annotations at the Service Interface is not working in native Mode #955
• Infer @AotProxyHint for @Scope beans #928
• Add preliminary Spring Batch support #203

⭐ Optimizations

... (truncated)

Commits

• 7760e5b Release 0.11.0
• ab0bb40 Improve Javadoc
• fe9fb9b Add API links to the refdoc
• 88c8c6e Document generateAot and generateTestAot Gradle tasks
• 589d943 Add missing source artifacts
• 2552439 Refine Native Hints documentation
• 2e10163 Update documentation for Bellsoft Liberica NIK usage
• 3d5c3be Add Javadoc for classes used for adding native configurations
• a5fa31f Move Mode class to org.springframework.nativex package
• 28b8ab0 Review AOT engine description
• Additional commits viewable in compare view

Updates spring-aot-maven-plugin from 0.10.1 to 0.11.0

Release notes

Sourced from spring-aot-maven-plugin's releases.

0.11.0

Upgrading from Spring Native 0.10

• GraalVM 21.3, Spring Boot 2.6 and Spring Cloud 2021.0 should be used as baselines.
• Java 8 is not supported anymore on GraalVM side, so it is not supported anymore on Spring Native side as well. But you will likely be able to compile most Java 8 applications with the Java 11 flavor of GraalVM.
• Please read the updated AOT engine documentation to understand how it behaves.
• Less hints are now required, for example those with import selector or condition trigger should be updated to use other ones.
• Hints with a trigger are now taken in account if the specified class is reachable by GraalVM static analysis, not just with a classpath check, except for annotations where the classpath check is still used.
• Native Build Tools configuration has evolved since the version used in now 0.9.8.
• Maven plugin now requires <extensions>true</extensions> and a dependency on org.junit.platform:unit-platform-launcher, see this documentation for more details.
• Gradle plugin is now automatically imported and configured when using the AOT plugin, so by default no need for additional configuration anymore.
• AccessBits is now deprecated and TypeAccess[] is used instead to specify @TypeHint access.
• NativeConfiguration SPI has been reworked to not use anymore the now deprecated TypeSystem.
• Extension points are now using META-INF/spring.factories instead of service loader to be discovered.
• ComponentProcessor extension point has been removed and should be replaced by BeanFactoryNativeConfigurationProcessor or BeanNativeConfigurationProcessor.
• Spring libraries using child application context (like Spring Cloud LoadBalancer) are not supported yet with the new AOT engine.
• Spring Cloud Bootstrap is no longer supported.
• FunctionalSpringApplication is no longer supported.
• While building a project that contains Spring Cloud Config Client, it is necessary to make sure that the configuration data source that it connects to (such as, Spring Cloud Config Server, Consul, Zookeeper, Vault, etc.) is available. For example, if you retrieve configuration data from Spring Cloud Config Server, make sure you have its instance running and available at the port indicated in the Config Client setup. This is necessary because the application context is being optimized at build time and requires the target environment to be resolved.
• Spring Cloud Function reflection configuration is now inferred so related hints can be removed.
• Spring AOT is now a forked process, in order to debug it, follow related documentation.

Changelog

In addition to the 0.11.0 changelog below, make sure to check 0.11.0-M1, 0.11.0-M2 and 0.11.0-RC1 ones to get a complete overview of the changes since Spring Native 0.10.

⭐ New Features

• Provide implementation of BeanFactoryNativeConfigurationProcessor for function types #1351
• Provide an SPI to exclude a bean definition to be written #1349
• Avoid creating reflection entries for java and primitive types. #1346
• Do not apply AOT plugin on POM projects #1344
• Use Flag renamed to TypeAccess instead of AccessBits in @TypeHint #1317
• Add logging to BeanDefinitionRegistrar #1306
• Use NativeConfigurationRegistry in NativeConfiguration #1279
• Add support for non Spring Boot tests #1170
• Restore Spring Integration support #1134
• Add support for Spring Data MongoDB (lazy loading) DocumentReference annotation. #875

⭐ Compatibility

• Register reflection configuration for JPA AttributeConverter implementations #1347
• Method signature types for methods of javax.persistence.AttributeConverter no longer included in configuration. #1329
• Regression on OAuth2 client and resource server with WebFlux #1291
• RestController with Annotations at the Service Interface is not working in native Mode #955
• Infer @AotProxyHint for @Scope beans #928
• Add preliminary Spring Batch support #203

⭐ Optimizations

... (truncated)

Commits

• 7760e5b Release 0.11.0
• ab0bb40 Improve Javadoc
• fe9fb9b Add API links to the refdoc
• 88c8c6e Document generateAot and generateTestAot Gradle tasks
• 589d943 Add missing source artifacts
• 2552439 Refine Native Hints documentation
• 2e10163 Update documentation for Bellsoft Liberica NIK usage
• 3d5c3be Add Javadoc for classes used for adding native configurations
• a5fa31f Move Mode class to org.springframework.nativex package
• 28b8ab0 Review AOT engine description
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #125.