* Use version catalog to drive Java platform
This commit incorporates the use of the Gradle version catalog as well
as the related plugins to automatically update the libs.version.toml
versions file with updated dependencies.
The UpdateProjectVersionPlugin is also updated to modify the spring
boot version property in the `libs.versions.toml` versions file rather than
gradle.properties.
Resolves#523
- Removes the use of spring-boot-dependencies to drive the
Java platform (spring-pulsar-dependencies). This is needed
to avoid chicken-egg problem when Spring Boot in turn has
a dependency on Spring Pulsar.
- Move integration tests into own sub-module
- The only place that still relies on Spring Boot is in the
integration tests and the samples.
- Update to Spring Boot 3.1.1-SNAPSHOT
* Prunes all non-core components
Remove modules:
- spring-pulsar-spring-boot-starter
- spring-pulsar-reactive-spring-boot-starter
- spring-pulsar-spring-boot-autoconfigure
- spring-pulsar-spring-cloud-stream-binder
- Remove config props plugins
- Update docs to point to Spring Boot config props
- Move intTest into spring-pulsar and spring-pulsar-reactive
* Replace refs from `spring-projects-experimental` to `spring-projects`
* Update spring-pulsar-spring-boot-starter to 0.2.1-SNAPSHOT
For both PulsarTemplate and ReactivePulsarTemplate:
* remove setSchema()
* add schema param in simple API
* add schema param in fluent API
Update all tests and samples accordingly
See #268
