怎样才能巩固常春藤版本管理,如家长POM< dependencyManagement>在Maven的? [英] How does one consolidate version management in Ivy, like parent-pom <dependencyManagement> in Maven?

查看:129
本文介绍了怎样才能巩固常春藤版本管理,如家长POM< dependencyManagement>在Maven的?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们有需要使用普通版本号许多项目。结果
什么是使用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?

推荐答案

正如您所指出的,我认为这就是问题所在了新的扩展功能已被设计来解决。

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

要完全诚实的,我不是在Maven的亲子模块风扇....但是,就像你有时我想钉我许多模块,以春常见的版本。

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.

这篇关于怎样才能巩固常春藤版本管理,如家长POM< dependencyManagement>在Maven的?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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