zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tamas Penzes (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ZOOKEEPER-2887) define dependency versions in build.xml to be easily overridden
Date Fri, 01 Sep 2017 18:32:00 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tamas Penzes updated ZOOKEEPER-2887:
------------------------------------
    Description: 
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.

  was:
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 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.


> define dependency versions in build.xml to be easily overridden
> ---------------------------------------------------------------
>
>                 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
>
> 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