Adds the ability to specify the Pulsar client version when running
the samples apps. Uses this new capability to add entries to the
check-samples.yml compatability test matrix to include Pulsar
4.0.x.
See #923
This commit updates the version of Pulsar to 3.3.2.
Also, in Pulsar 3.3.2 the schema validation of an outgoing message value
happens later than it did previously. This requires the PulsarTemplate
to widen the try/catch net so that when this happens the producer is
closed properly. The backing change in Pulsar 3.3.2 can be seen here
f3c177e224 (diff-095bc2359e03726e031d8c2f210560c6a3218f48a969b0f75a2482e25cd54744R69)
* Update to Pulsar 3.3.1
* Handles deprecation to PulsarClient.getPartitionsForTopic(String)
* Adds support to PulsarClientProxy for newly added
PulsarClient.getPartitionsForTopic(String, boolean)
* Add deprecation note to "What's New" doc
Resolves#767
This commit adds support for a user-provided Jackson ObjectMapper to be
used when de/serializing JSON messages.
Additionally, adds Gradle test fixtures to the spring-pulsar module and
deprecates the UserRecord and UserPojo in spring-pulsar-test in favor
of their equivalent in the test fixture.
See #723
* Remove Brave from java platform
This commit removes Brave from being managed directly in the Java
Platform. Because the Brave version is already handled by Micrometer
Tracing BOM (which we import) there is no need to manage this
directly.
* Add observations back in sample failover app
This commit adds back in the observation related dependencies into the
sample-failover-custom-router sample app. They were removed temporarily
as Spring Boot 3.3.0-SNAPSHOT had a bug when they bumped to Brave 6.0.1.
Additionally:
-------------
* Add in template and listener observation-enabled properties as
Spring Boot is currently setting these to false byu default.
* Remove observation related dependencies from the sample functions app
as they were not intended to be there in the first place.
This commit updates to the latest Brave version (6.0.1). This revealed a
strange classloader issue for Zipkin2.Span when running the failover
sample app during the 'test' target. To get around this issue the
tracing dependencies are temporarily commented out in the failover
sample app.
This commit adjust the `spring.docker.compose.file` property value to
allow running the sample via IntelliJ "run" button or from command line
via `./gradlew bootRun`.
* 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
