You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Raul Gutierrez Segales (JIRA)" <ji...@apache.org> on 2014/04/18 22:43:15 UTC
[jira] [Created] (ZOOKEEPER-1913) Invalid manifest files due to
bogus revision property value
Raul Gutierrez Segales created ZOOKEEPER-1913:
-------------------------------------------------
Summary: 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.5.0
Reporter: Raul Gutierrez Segales
Assignee: Raul Gutierrez Segales
Fix For: 3.5.0
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)