v3.2.5 Feature Update

3.2.5 (02/21/2023)

• Add official support for Kafka versions 3.0.x through 3.4.x
• gquintana added the following method to KafkaTestUtils to allow for additional control over the records being produced.
  Thanks for the contribution!

public List<ProducedKafkaRecord<byte[], byte[]>> produceRecords(final Collection<ProducerRecord<byte[], byte[]>> records)

Internal dependency updates

• JUnit5 from 5.8.2 to 5.9.2
• Fix CI Build scripts

v3.2.4 Bugfix release

3.2.4 (03/01/2022)

Bugfixes

• ISSUE-49 PR-63 Zookeeper AdminServer will no longer be started. This allows for more easily running tests in parallel. Thanks @gquintana for the contribution!

Internal dependency updates

• JUnit4 from 4.13 to 4.13.2
• JUnit5 from 5.7.2 to 5.8.2

v.3.2.3 Add support for Kafka 2.7.x and 2.8.x

3.2.3 (07/27/2021)

Features

• Officially added support for Kafka versions 2.7.x, and 2.8.x

Internal dependency updates

• JUnit5 from 5.6.2 to 5.7.2

v3.2.2 Validate against Kafka versions 2.5.x and 2.6.x

3.2.2 (08/13/2020)

Features

• PR-46 Officially added support for Kafka versions 2.5.x, 2.6.x.

Internal dependency updates

• JUnit5 from 5.6.0 to 5.6.2

v3.2.1 Bugfix Release

3.2.1 (02/03/2020)

PR-42

Features

• Officially added support for Kafka versions 2.1.x, 2.2.x, 2.3.x, 2.4.x.
  • (Documentation change only)

Bugfix

• Fixes bug in ZookeeperTestServer.start() where calling start on an already running instance caused the instance to be restarted instead of being a no-operation.
  This caused issues with Kafka version 2.1.x on startup and shutdown causing tests to hang.

Internal dependency updates

• JUnit4 from 2.12 to 2.13
• JUnit5 from 5.3.2 to 5.6.0

v3.2.0 Feature Release

3.2.0 (11/13/2019)

• ISSUE-38 Optionally allow for explicitly defining which ports kakfa brokers listen on.

Configuring explicit ports for broker(s)

Optionally if you require specific ports for the Kafka brokers to listen on, you can use the BrokerListener.onPorts(...) method when registering a listener.

Not calling the onPorts() method will have the broker(s) listen on randomly assigned ports (defaults to previous behavior).

    /**
     * This is an example of how to start a broker on an explicitly defined port of 1234.
     * The onPorts() can be called on any of the above listener types.
     */
    @RegisterExtension
    public static final SharedKafkaTestResource sharedKafkaTestResource = new SharedKafkaTestResource()
        .registerListener(new PlainListener().onPorts(1234));

    /**
     * If you are running a multi-broker cluster, you will need to pass a unique port for each 
     * broker in the cluster.
     * 
     * This example will have 2 brokers where:
     *   The first broker is listening on port 1234.
     *   The second broker is listening on port 4321.
     */
    @RegisterExtension
    public static final SharedKafkaTestResource sharedKafkaTestResource = new SharedKafkaTestResource()
        .withBrokers(2)
        .registerListener(new PlainListener().onPorts(1234, 4321));

v3.1.2 Bugfix release

3.1.2 (11/08/2019)

• ISSUE-36 Temporary directories should now be cleaned up properly on JVM shutdown.

Maintenance Release

3.1.1 (03/22/2019)

• Replace internal uses of Guava with JDK-comparable methods so that if a transitive dependency on Curator resolves to a more recent version that shades Guava this library will not break.

Thanks @mkobit !

Feature Release

3.1.0 (12/13/2018)

• Officially support Kafka 2.0.x
• KafkaTestUtils.produceRecords() and its variants now set producer configuration "acks" to "all"
• Update Kafka-JUnit5 junit dependency from 5.1.1 to JUnit 5.3.2
• Kafka Connection Strings now include the protocol prefix.
• Default configured host changed from '127.0.0.1' to 'localhost'
• Add support for registering PLAINTEXT, SSL, SASL_PLAIN, and SASL_SSL listeners on internal kafka brokers. See module READMEs for more details and usage instructions.

Bugfix Release

3.0.1 (06/20/2018)

• Issue-16 Bugfix for re-using the same SharedKafkaTestResource instance multiple times, as might happen if you run a test multiple times.
• Update checkstyle plugin version to 3.0.0