[
https://issues.apache.org/jira/browse/KAFKA-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Homan updated KAFKA-1308:
-------------------------------
Attachment: KAFKA-1308-2.patch
Looks like this works without the pom. I've updated Jun's patch to change the
Kafka version string to be SNAPSHOTed, since everything but an RC should be a
snapshot. As part of testing, I published snapshots of 0.8.1.1 snapshots and
used them against SAMZA (SAMZA-284).
> 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-2.patch, KAFKA-1308-8.1.1.patch,
> KAFKA-1308.patch, KAFKA-1308.patch, kafka-1308_v2_0.8.1.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)
