[jira] [Commented] (ZOOKEEPER-297) centralize version numbering in the source/build

["Diego de Oliveira (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624285#comment-13624285 ] 

Diego de Oliveira commented on ZOOKEEPER-297:
---------------------------------------------

I did some hack with ant and template text processing. 

The required files (configure.ac.in, include/zookeeper_version.h.in) are now generated from a .in template. This template contains the placeholder that must be replaced by some "build.xml" property.

The target "compile-native" now depends on "process-template", that regenerate the final file from the template. 
                
> 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.1.0
>            Reporter: Patrick Hunt
>            Priority: Minor
>             Fix For: 3.5.0
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira