[
https://issues.apache.org/jira/browse/ZOOKEEPER-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107733#comment-13107733
]
Thomas Koch commented on ZOOKEEPER-297:
---------------------------------------
This discussion explains how one could make a version number available to an
application without generating a Version.java file:
http://stackoverflow.com/questions/2469922/generate-a-version-java-file-in-maven
It also points to a maven plugin that can provide revision numbers for SVN or
GIT:
http://mojo.codehaus.org/buildnumber-maven-plugin/
I propose to implement the described solution after we've moved to maven.
Together with the following maven plugin we can maybe move to having only one
place for the version number:
http://mojo.codehaus.org/properties-maven-plugin/usage.html
This would imply however that the C build could somehow grab the version number
from a java properties file.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
