[
https://issues.apache.org/jira/browse/ZOOKEEPER-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13951763#comment-13951763
]
Hudson commented on ZOOKEEPER-297:
----------------------------------
FAILURE: Integrated in ZooKeeper-trunk #2271 (See
[https://builds.apache.org/job/ZooKeeper-trunk/2271/])
ZOOKEEPER-297. centralize version numbering in the source/build (Diego de
Oliveira via michim) (michim:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1582941)
* /zookeeper/trunk/CHANGES.txt
* /zookeeper/trunk/build.xml
* /zookeeper/trunk/src/c/configure.ac
* /zookeeper/trunk/src/c/configure.ac.in
* /zookeeper/trunk/src/c/include/zookeeper_version.h
* /zookeeper/trunk/src/c/include/zookeeper_version.h.in
> 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,
> build_version2.patch, build_version3.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)
