[
https://issues.apache.org/jira/browse/KAFKA-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14042700#comment-14042700
]
Jakob Homan commented on KAFKA-1308:
------------------------------------
We're still blocked on the Samza release even with this patch because the
snapshots I'm publishing are being cleaned on a daily basis. To get around
this I would like to publish the 0.8.1.1 release to the main maven site using
this patch:
* Use the rc1 tgz that was voted in as 0.8.1.1 as the release
(https://people.apache.org/~joestein/kafka-0.8.1.1-candidate1/kafka-0.8.1.1-src.tgz)
* Apply the patch, remove the -SNAPSHOT
* Run ./gradlew uploadArchivesAll against the main repo, publishing the test
jar and all of the original jars.
This is ASF-ok since this patch does not change anything about the code that
was generated, just publishes an extra jar on top of what was previously
published. This will unblock us since we can then pull from the main repo.
The alternative is to wait for Kafka to release a 0.8.1.2 (or whatever), which
would add an extra week or more for the vote to run.
> 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)
