[
https://issues.apache.org/jira/browse/KAFKA-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037468#comment-14037468
]
Chris Campbell commented on KAFKA-1308:
---------------------------------------
For what its worth, the main reason I created a separate jar for the patch was
this message, which seemed to imply that it's not useful to ship the test cases:
http://mail-archives.apache.org/mod_mbox/kafka-users/201308.mbox/%3ccaoejijgjppc+m+xqeyrninjcmq9vsjfzp3efhvaknbdjndl...@mail.gmail.com%3E
If there are other classes that people want to use, it seems better to include
them in this separately published jar to help make it clear what is meant to be
fit for public consumption, rather than just a wholesale dump of test classes.
But it's not a big deal either way :)
> Publish jar of test utilities to Maven
> --------------------------------------
>
> Key: KAFKA-1308
> URL: https://issues.apache.org/jira/browse/KAFKA-1308
> Project: Kafka
> Issue Type: Wish
> Affects Versions: 0.8.1
> Reporter: Martin Kleppmann
> Priority: Blocker
> Fix For: 0.8.2
>
> Attachments: KAFKA-1308.patch
>
>
> For projects that use Kafka, and want to write tests that exercise Kafka (in
> our case, Samza), it's useful to have access to Kafka's test utility classes
> such as kafka.zk.EmbeddedZookeeper and kafka.utils.TestUtils. We can use
> {{./gradlew testJar}} to build jar files that contain those classes, but as
> far as I know, these are currently not made available in a binary release.
> At the moment, we have to check those kafka*-test.jar files into the Samza
> repository. To avoid that, would it be possible to publish those jars of
> tests to Maven, so that they fit into the normal dependency management?
> Or perhaps, if publishing the tests themselves is not appropriate, we could
> move the test utilities into a separate module that is published, and make
> the tests depend on that module?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
