[jira] [Comment Edited] (KAFKA-19050) kafka-streams-integration-tests artifact is empty

["Utku Aydin (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-19050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17938906#comment-17938906 ] 

Utku Aydin edited comment on KAFKA-19050 at 3/27/25 11:32 AM:
--------------------------------------------------------------

[~chia7712] I'm not saying it should be moved to production necessarily, but the tests can be published within the jar. In that case, deprecation rules can be ignored since it would be in the test scope, but we could also assume that it would always be in working condition/in line with the current state of the streams module since these tests are required to pass for a release anyway. Meaning, it would be maintained as a product of the release process and be available to users for their own testing.

Of course another approach would be to make it a public API, that way it can be used within the project and also users would have deprecation info. But I assume that would take much more time, so I would be in favor of at least publishing the test scope within the jar since it is empty at the moment, and discuss turning it into a public API later on.


was (Author: JIRAUSER304555):
[~chia7712] I'm not saying it should be moved to production necessarily, but the tests can be published within the jar. In that case, deprecation rules can be ignored since it would be in the test scope, but we could also assume that it would always be in working condition/in line with the current state of the streams module since these tests are required to pass for a release anyway. Meaning, it would be maintained as a product of the release process and be available to users for their own testing.

Of course another approach would be to make it a public API, that way it can be used within the project and also users would have deprecation info. But I assume that would take much more time, so I would be in favor of at least publishing the test scope within the jar since it is empty at the moment, and think about turning it into a public API later on.

> kafka-streams-integration-tests artifact is empty
> -------------------------------------------------
>
>                 Key: KAFKA-19050
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19050
>             Project: Kafka
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 4.0.0
>            Reporter: Utku Aydin
>            Priority: Major
>
> Not sure whether this was intended or not but currently the release process releases an artifact with an empty jar containing only the manifest for the kafka-streams-integration-tests module. Since these tests are now in their own module, I think it's an opportunity to make them available to end-users as well. Personally, I would like to use EmbeddedKafkaCluster from org.apache.kafka.streams.integration.utils for my own integration tests since io.github.embeddedkafka is no longer being maintained.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)