[
https://issues.apache.org/jira/browse/ZOOKEEPER-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13951623#comment-13951623
]
Hadoop QA commented on ZOOKEEPER-297:
-------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12637300/build_version.patch
against trunk revision 1582572.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 4 new or modified tests.
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1994//console
This message is automatically generated.
> centralize version numbering in the source/build
> ------------------------------------------------
>
> Key: ZOOKEEPER-297
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-297
> Project: ZooKeeper
> Issue Type: Improvement
> Components: build
> Affects Versions: 3.5.0
> Reporter: Patrick Hunt
> Assignee: Diego de Oliveira
> Priority: Minor
> Labels: patch
> Fix For: 3.5.0
>
> Attachments: build_version.patch, build_version.patch
>
>
> There are now three locations in the source repository that store the version
> number of the code:
> 1) build.xml
> 2) configure.ac
> 3) zookeeper_version.h
> these all have to be managed when releasing/branching/etc... would be better
> if there were just one place - at the very least the configure.ac should be
> used to generate the version for zookeeper_version.h.
> Can we do a better job (ie less) at this?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
