[
https://issues.apache.org/jira/browse/ZOOKEEPER-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13974821#comment-13974821
]
Hudson commented on ZOOKEEPER-1913:
-----------------------------------
FAILURE: Integrated in ZooKeeper-trunk #2295 (See
[https://builds.apache.org/job/ZooKeeper-trunk/2295/])
ZOOKEEPER-1913. Invalid manifest files due to bogus revision property value
(Raul Gutierrez Segales via michim) (michim:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1588584)
* /zookeeper/trunk/CHANGES.txt
* /zookeeper/trunk/build.xml
> Invalid manifest files due to bogus revision property value
> -----------------------------------------------------------
>
> Key: ZOOKEEPER-1913
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1913
> Project: ZooKeeper
> Issue Type: Bug
> Components: build
> Affects Versions: 3.4.6, 3.5.0
> Reporter: Raul Gutierrez Segales
> Assignee: Raul Gutierrez Segales
> Fix For: 3.4.7, 3.5.0
>
> Attachments: ZOOKEEPER-1913.patch
>
>
> 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:
> {noformat}
> $ 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)
> {noformat}
> since it doesn't seem happen with older java/ant combinations.
> Nonetheless, it seems like the right thing is to explicitly ignore stderr.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
