You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2017/10/04 16:55:00 UTC
[jira] [Updated] (ZOOKEEPER-2887) define dependency versions in
build.xml to be easily overridden in build.properties
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-2887:
------------------------------------
Fix Version/s: 3.5.4
> define dependency versions in build.xml to be easily overridden in build.properties
> -----------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2887
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2887
> Project: ZooKeeper
> Issue Type: Improvement
> Components: build
> Reporter: Tamas Penzes
> Assignee: Tamas Penzes
> Fix For: 3.5.4, 3.6.0
>
>
> Dependency versions are defined in ivy.xml, which is suboptimal since it is hard to override them from a script.
> If we defined the versions in the main build.xml (just as we do with audience-annotations.version) and use variables in ivy.xml then we could easily override the versions with creating a build.properties file, which mechanism is already built in.
> This way the dependency versions could be replaced by sed or any simple command line tool.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)