68f59a0d40
Previously, dependency management for JNA was provided by spring-boot-dependencies so it affected users' applications. It was original added for Elasticsearch but is no longer needed for that purpose. We use JNA in spring-boot-buildpack-platform which is used by our Gradle and Maven plugins and should not affect an application's use of JNA. This commit moves management of JNA from spring-boot-dependencies into spring-boot-parent. This means that users' applications will now be free to use whatever version of JNA meets their needs while still controlling the version used for image building via Gradle or Maven. Closes gh-20156 |
||
|---|---|---|
| .. | ||
| spring-boot | ||
| spring-boot-actuator | ||
| spring-boot-actuator-autoconfigure | ||
| spring-boot-autoconfigure | ||
| spring-boot-cli | ||
| spring-boot-dependencies | ||
| spring-boot-devtools | ||
| spring-boot-docs | ||
| spring-boot-parent | ||
| spring-boot-properties-migrator | ||
| spring-boot-starters | ||
| spring-boot-test | ||
| spring-boot-test-autoconfigure | ||
| spring-boot-tools | ||