4.0.2: Bugfix release

This release fixes #44: Flow ID was not sent to nakadi

4.0.1: Bugfix release

#40: MockNakadiPublishingClient.getSentEvents(...) threw a NPE if no events of that type have been sent. Instead, it now returns an empty list.

This has no effect on productive code, just on your testing (if you are using the MockNakadiPublishingClient).

4.0.0: Improved, customizable Flyway setup

This release contains two major changes:

First, we've split the library in two: A Spring boot starter lib and a core lib, that is mostly agnostic of database schemata, Spring, JDBC and autowiring. For the moment, we neither support nor recommend using the core lib as a stand alone artifact. We also only guarantee semantic versioning for the whole project, not for the core lib as stand alone artifact.

Second and more importantly:
The starter now autoconfigures its Flyway instance to use the Flyway DataSource configured by the host application, not its @Primary DataSource. You can override this by annotating a DataSource as @NakadiProducerDataSource.

To make your schema maintenance even more configurable, you can now also define a spring bean of type FlywayCallback and annotate it with @NakadiProducerFlywayCallback. The interface provide several hook into the schema management life cycle that may, for example, be used to SET ROLE migrator before and RESET ROLE after each migration.

How to migrate from version 3.x.x

We consider this a major release, because the library will now pick your Flyway DataSource instead of your @Primary DataSource when executing it's database schema migrations. This may result in migration scripts being executed using a different user name as before. If your want to force the library to use your @Primary DataSource, annotate it with @NakadiProducerDataSource.

3.0.1 Bugfix release

This release fixes issue #27: The Autoconfiguration will not instantiate the StupsTokenComponent accessTokenProvider Bean anymore when the host application already configured its own NakadiPublishingClient - for example a MockNakadiPublishingClient.

3.0.0 Better host application integration

• now uses a separate flyway instance to not collide with your application's flyway config
• massively reduced the dependency footprint
• better testing support
• No use of JPA anymore

How to migrate from v2.x.x:

• MUST: Remove the flyway configuration from your application.properties
• MAY: Remove the entity scanning config from your Spring configuration
• MAY: Remove the @EnableJpaRepositories from your Spring configuration
• MAY: Migrate your tests to the new MockNakadiPublishingClient

2.0.0 – business event support

Added support for business events ... with some API changes.

1.0.1 configuration fixes

• Fixes broken autoconfiguration when no tracer or no tokens library is on the class path
• fixed reading of multiple scopes

Initial Release v1.0

Merge pull request #9 from zalando-incubator/LBJ-208

Preparations for Release 1.0