zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Hunt (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2887) define dependency versions in build.xml to be easily overridden in build.properties
Date Wed, 04 Oct 2017 17:09:00 GMT

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

Patrick Hunt commented on ZOOKEEPER-2887:
-----------------------------------------

lgtm, commited. One thing Tamas - in future when cherry picking use the "-x" option. Thanks!

> 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, 3.4.11
>
>
> 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)

Mime
View raw message