3.1.0.RELEASE

Changes between 3.0.1.RELEASE and 3.1.0.RELEASE

This minor release brings a new feature and dependency upgrades. Note the dependency upgrades contain a vulnerability fix for the JSON mapping library Jackson. All users are encouraged to upgrade to this release.

Support for all dynamic shovel properties

GitHub issue: #143

Bump dependencies

The blocking client depends on Spring Framework 5.1.4. The ReactorNettyClient depends on Reactor Core 3.2.5 and Reactor Netty 0.8.4.

GitHub issue: #146

Bump Jackson to 2.9.8

The upgrade addresses a CVE.

GitHub issue: #145

3.1.0.RC1

Changes between 3.0.1.RELEASE and 3.1.0.RC1

This pre-release brings a new feature and dependency upgrades. Note the dependency upgrades contain a vulnerability fix for the JSON mapping library Jackson.

Support for all dynamic shovel properties

GitHub issue: #143

Bump dependencies

The blocking client depends on Spring Framework 5.1.4. The ReactorNettyClient depends on Reactor Core 3.2.5 and Reactor Netty 0.8.4.

GitHub issue: #146

Bump Jackson to 2.9.8

The upgrade addresses a CVE.

GitHub issue: #145

v3.0.1.RELEASE

Changes between 3.0.0 and 3.0.1

This patch release contains 2 bug fixes and dependency upgrades. All users are encouraged to upgrade to this version.

Closing reason isn't propagated to client

GitHub issue: #142

Reject Shovel declarations with empty publish property maps

GitHub issue: #139

Bump dependencies

The blocking client depends on Spring Framework 5.1.3. The ReactorNettyClient depends on Reactor Core 3.2.3 and Reactor Netty 0.8.3.

GitHub issue: #141

3.0.0.RELEASE

Changes between 2.1.0 and 3.0.0

This major release brings support for topic permissions, bumps dependencies, and removes Spring WebFlux ReactiveClient. The ReactorNettyClient is now the only reactive client. See below for breaking changes. All users are encouraged to upgrade to this version.

Support topic permissions

GitHub issue: #132

Bump dependencies

Jackson has been bumped to 2.9.7. The blocking client depends on Spring Framework 5.1.1. The ReactorNettyClient depends on Reactor Core 3.2.1 and Reactor Netty 0.8.1.

GitHub issue: #134

Remove ReactiveClient based on Spring WebFlux

GitHub issue: #129

Breaking changes

• ReactiveClient removal: use ReactorNettyClient instead. The API is almost identical.
• ReactorNettyClient:
  • With the upgrade to 0.8, Reactor Netty now uses the reactor.netty package instead of reactor.ipc.netty. This can affect those configuring their HttpClient with ReactorNettyClientOptions.
  • ReactorNettyClientOptions#errorHandler has been removed in favor of ReactorNettyClientOptions#onResponseCallback, a BiConsumer<? super HttpEndpoint, ? super HttpResponse> onResponseCallback that gives more control over the response.

3.0.0.RC1

Changes between 2.1.0 and 3.0.0.RC1

This is a pre-release for 3.0.0. It brings support for topic permissions, bumps dependencies, and removes Spring WebFlux ReactiveClient. The ReactorNettyClient is now the only reactive client. See below for breaking changes.

Support topic permissions

GitHub issue: #132

Bump dependencies

Jackson has been bumped to 2.9.7. The blocking client depends on Spring Framework 5.1.1. The ReactorNettyClient depends on Reactor Core 3.2.1 and Reactor Netty 0.8.1.

GitHub issue: #134

Remove ReactiveClient based on Spring WebFlux

GitHub issue: #129

Breaking changes

• ReactiveClient removal: use ReactorNettyClient instead. The API is almost identical.
• ReactorNettyClient:
  • With the upgrade to 0.8, Reactor Netty now uses the reactor.netty package instead of reactor.ipc.netty. This can affect those configuring their HttpClient with ReactorNettyClientOptions.
  • ReactorNettyClientOptions#errorHandler has been removed in favor of ReactorNettyClientOptions#onResponseCallback, a BiConsumer<? super HttpEndpoint, ? super HttpResponse> onResponseCallback that gives more control over the response.

2.1.0.RELEASE

Changes between 2.0.2 and 2.1.0

This release ships a new reactive client based on Reactive Netty, deprecates the ReactiveClient based on Spring's WebClient, and makes transitive dependencies optional. Because of this latter change, existing applications may need to adapt their dependencies (see below for details).

Users of previous versions are encouraged to use this release. Users of the ReactiveClient are encouraged to upgrade to the new ReactorNettyClient (their API is almost identical).

Thanks to @artembilan, @jokogr, and @sparcv9 for their contribution on this pre-release.

Introduce new reactive client based on Reactive Netty

The new ReactorNettyClient provides an asynchronous, reactive API based on Reactor's Mono and Flux API. Users in need of a reactive API should use ReactorNettyClient instead of ReactiveClient. Users of ReactorClient should upgrade to ReactorNettyClient.

GitHub PR: #123

Make dependencies optional

This is a potential breaking change in existing applications, depending on the way dependencies are managed. From now on, declaring Hop dependency isn't enough, you also need to declare the dependencies that the client you're using depends on. This is all documented in the readme.

This change avoids pulling unnecessary dependencies when using only one of the clients Hop provides.

GitHub issue: #124

Deprecate ReactiveClient

ReactiveClient uses internally Spring WebFlux WebClient which pulls a fair amount of dependencies and is supposed to be used exclusively in Spring applications. To avoid bloating in simple, lightweight applications that rely on Hop, developers are encouraged to use the lighter Reactive Netty-based ReactorNettyClient.

ReactiveClient will be definitely removed in Hop 3.0.

GitHub issues: #122, #128

Add source and destination exchange key for shovel details

Feature contributed by @sparcv9.

GitHub PR: #130

Expose ack-mode in ShovelDetails

Feature contributed by @jokogr.

GitHub PR: #121

2.1.0.RC1

Changes between 2.0.2 and 2.1.0.RC1

This pre-release ships a new reactive client based on Reactive Netty, deprecates the ReactiveClient based on Spring's WebClient, and makes transitive dependencies optional. Because of this latter change, existing applications may need to adapt their dependencies (see below for details).

Users of previous versions are encouraged to test this pre-release. Users of the ReactiveClient are encouraged to experiment with the new ReactorNettyClient client (their API is almost identical) and should consider upgrading to it.

Thanks to @artembilan and @jokogr for their contribution on this pre-release.

Introduce new reactive client based on Reactive Netty

The new ReactorNettyClient provides an asynchronous, reactive API based on Reactor's Mono and Flux API. Users in need of a reactive API should use ReactorNettyClient instead of ReactiveClient. Users of ReactorClient should upgrade to ReactorNettyClient.

GitHub PR: #123

Make dependencies optional

This is a potential breaking change in existing applications, depending on the way dependencies are managed. From now on, declaring Hop dependency isn't enough, you also need to declare the dependencies that the client you're using depends on. This is all documented in the readme.

This change avoids pulling unnecessary dependencies when using only one of the clients Hop provides.

GitHub issue: #124

Deprecate ReactiveClient

ReactiveClient uses internally Spring WebFlux WebClient which pulls a fair amount of dependencies and is supposed to be used exclusively in Spring applications. To avoid bloating in simple, lightweight applications that rely on Hop, developers are encouraged to use the lighter Reactive Netty-based ReactorNettyClient.

ReactiveClient will be definitely removed in Hop 3.0.

GitHub issues: #122, #128

Expose ack-mode in ShovelDetails

Feature contributed by @jokogr.

GitHub PR: #121

2.0.2.RELEASE

Changes between 2.0.1 and 2.0.2

This is a patch release with an update of dependencies. All users of 2.0.x are encouraged to upgrade to this version.

Bump dependencies

HOP now uses Commons HTTP Client 4.5.5, Jackson 2.9.5, Spring Framework 5.0.6, and Reactor 3.1.7.

GitHub issue: #126

1.3.2.RELEASE

Changes between 1.3.1 and 1.3.2

This is a patch release with an update of dependencies. All users of the 1.x.x series are encouraged to upgrade to this version.

Bump dependencies

HOP now uses Commons HTTP Client 4.5.5, Jackson 2.9.5, and Spring Framework 4.3.17.

GitHub issue: #125

2.0.1.RELEASE

Changes between 2.0.0 and 2.0.1

This is a patch release with a bug fix and an update of dependencies. All users of 2.0.0 are encouraged to upgrade to this version.

Set Content-Type header properly

The Content-Type header was set twice.

GitHub issue: #114

Upgrade dependencies

HOP now uses Commons HTTP Client 4.5.3, Jackson 2.9.2, Spring Framework 5.0.1, and Reactor 3.1.1.

GitHub issue: #116