Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-1901

Move Kafka version to be generated in code by build (instead of in manifest)

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 0.8.2.0
    • 0.9.0.0
    • None
    • None

    Description

      With 0.8.2 (rc2), I've started seeing this warning in the logs of apps deployed to our staging (both server and client):

      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

      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.

      Attachments

        1. KAFKA-1901.patch
          14 kB
          Manikumar
        2. KAFKA-1901_2015-06-26_13:16:29.patch
          14 kB
          Manikumar
        3. KAFKA-1901_2015-07-10_16:42:53.patch
          14 kB
          Manikumar
        4. KAFKA-1901_2015-07-14_17:59:56.patch
          15 kB
          Manikumar
        5. KAFKA-1901_2015-08-09_15:04:39.patch
          18 kB
          Manikumar
        6. KAFKA-1901_2015-08-20_12:35:00.patch
          17 kB
          Manikumar

        Activity

          People

            omkreddy Manikumar
            jbrosenberg@gmail.com Jason Rosenberg
            Joel Jacob Koshy Joel Jacob Koshy
            Votes:
            3 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: