[
https://issues.apache.org/jira/browse/KAFKA-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619138#comment-13619138
]
Dragos Manolescu commented on KAFKA-826:
----------------------------------------
I'm sorry you've had problems with this patch. You should be good to go:
seac02jh0rjdkq4 ~/Repos/kafka% git status
[92]
# On branch 0.8
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
#
# .idea_modules/
nothing added to commit but untracked files present (use "git add" to track)
mseac02jh0rjdkq4 ~/Repos/kafka% patch -p1 --dry-run <
../kafka-fix-for-826-take2.patch
[93]
patching file core/src/main/scala/kafka/cluster/Partition.scala
patching file
core/src/main/scala/kafka/consumer/ZookeeperConsumerConnector.scala
patching file core/src/main/scala/kafka/controller/KafkaController.scala
patching file core/src/main/scala/kafka/log/Log.scala
patching file core/src/main/scala/kafka/network/RequestChannel.scala
patching file core/src/main/scala/kafka/producer/async/ProducerSendThread.scala
patching file core/src/main/scala/kafka/server/AbstractFetcherThread.scala
patching file core/src/main/scala/kafka/server/ReplicaManager.scala
patching file core/src/main/scala/kafka/server/RequestPurgatory.scala
patching file core/src/test/scala/unit/kafka/metrics/KafkaTimerTest.scala
patching file project/Build.scala
patching file project/build/KafkaProject.scala
> Make Kafka 0.8 depend on metrics 2.2.0 instead of 3.x
> -----------------------------------------------------
>
> Key: KAFKA-826
> URL: https://issues.apache.org/jira/browse/KAFKA-826
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8
> Reporter: Neha Narkhede
> Assignee: Jun Rao
> Priority: Blocker
> Labels: build, kafka-0.8, metrics
> Attachments: kafka-fix-for-826.patch
>
>
> In order to mavenize Kafka 0.8, we have to depend on metrics 2.2.0 since
> metrics 3.x is a huge change as well as not an officially supported release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
