You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Manikumar Reddy (JIRA)" <ji...@apache.org> on 2015/08/09 11:37:46 UTC
[jira] [Updated] (KAFKA-1901) Move Kafka version to be generated in
code by build (instead of in manifest)
[ https://issues.apache.org/jira/browse/KAFKA-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manikumar Reddy updated KAFKA-1901:
-----------------------------------
Attachment: KAFKA-1901_2015-08-09_15:04:39.patch
> Move Kafka version to be generated in code by build (instead of in manifest)
> ----------------------------------------------------------------------------
>
> Key: KAFKA-1901
> URL: https://issues.apache.org/jira/browse/KAFKA-1901
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.2.0
> Reporter: Jason Rosenberg
> Assignee: Manikumar Reddy
> Attachments: KAFKA-1901.patch, KAFKA-1901_2015-06-26_13:16:29.patch, KAFKA-1901_2015-07-10_16:42:53.patch, KAFKA-1901_2015-07-14_17:59:56.patch, KAFKA-1901_2015-08-09_15:04:39.patch
>
>
> With 0.8.2 (rc2), I've started seeing this warning in the logs of apps deployed to our staging (both server and client):
> {code}
> 2015-01-23 00:55:25,273 WARN [async-message-sender-0] common.AppInfo$ - Can't read Kafka version from MANIFEST.MF. Possible cause: java.lang.NullPointerException
> {code}
> The issues is that in our deployment, apps are deployed with single 'shaded' jars (e.g. using the maven shade plugin). This means the MANIFEST.MF file won't have a kafka version. Instead, suggest the kafka build generate the proper version in code, as part of the build.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)