如何在 Ivy 中整合版本管理,比如 parent-pom <dependencyManagement>在 Maven? [英] How does one consolidate version management in Ivy, like parent-pom <dependencyManagement> in Maven?

查看:19
本文介绍了如何在 Ivy 中整合版本管理,比如 parent-pom <dependencyManagement>在 Maven?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们有很多项目需要使用通用版本号.
使用 Ant/Ivy 执行此操作的最佳实践是什么?您是否只是从 Ant 继承了一堆包含版本号的属性,还是有更正式的机制,如 Maven?

We have many projects that need to use common version numbers.
What is best practice for doing this with Ant/Ivy? Do you just inherit a wad of properties from Ant that have the version numbers in them, or is there a more formal mechanism a la Maven?

推荐答案

正如你所指出的,我认为这是新的 extends 功能旨在解决.

As you've pointed out I think this is the problem which the new extends functionality has been designed to solve.

老实说,我不喜欢 Maven 中的父子模块......但是,就像你一样,有时我想将我的很多模块固定到 Spring 的通用版本中.

To be completely honest I'm not a fan of parent-child modules in Maven.... However, just like you sometimes I want to nail lots of my modules to a common version of Spring.

我使用的解决方案是定义一组 属性在我共享的 ivysettings 文件中.这使我的常春藤特定属性与我的 ANT 构建属性分开.

The solution I used was to have a set of properties defined in my shared ivysettings file. This keeps my ivy specific properties separate from my ANT build properties.

这篇关于如何在 Ivy 中整合版本管理,比如 parent-pom <dependencyManagement>在 Maven?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆