Uploaded image for project: 'ZooKeeper'
  1. ZooKeeper
  2. ZOOKEEPER-1913

Invalid manifest files due to bogus revision property value

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 3.4.6, 3.5.0
    • 3.4.7, 3.5.0
    • build
    • None

    Description

      Without the proposed patch, I get invalid manifests because stderr is added to the revision property. I think this might be something specific to my setup though:

          $ java -version
          Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=utf8
          java version "1.7.0_51"
          OpenJDK Runtime Environment (fedora-2.4.5.1.fc20-x86_64 u51-b31)
          OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode)
      

      since it doesn't seem happen with older java/ant combinations.

      Nonetheless, it seems like the right thing is to explicitly ignore stderr.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            rgs Raúl Gutiérrez Segalés Assign to me
            rgs Raúl Gutiérrez Segalés
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment