Skip to content

TopicConfig annotation name clash #351

@fvaleri

Description

@fvaleri

This is a bit ugly:

@Test
public void shouldAlterConfigs(KafkaCluster cluster,
                               @io.kroxylicious.testing.kafka.junit5ext.TopicConfig(name = TopicConfig.RETENTION_MS_CONFIG, value = "604800000") Topic t1,
                               @io.kroxylicious.testing.kafka.junit5ext.TopicConfig(name = TopicConfig.CLEANUP_POLICY_CONFIG, value = "delete") Topic t2) {
...

Maybe we can deprecate this annotation and rename to avoid the name clash with Kafka.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions