Maven的常春藤或从蚂蚁管理依赖？ [英] Maven or Ivy for Managing Dependencies from Ant?

问题描述

我想知道，从蚂蚁管理项目依赖关系的最佳途径。什么是Maven的Ant任务常春藤和利弊？

I was wondering about the best way to manage projects dependencies from ant. What are the pros and cons of the Maven Ant task and of Ivy?

推荐答案

既然你想要做的是依赖管理添加到现有的Ant项目，这是precisely什么常春藤的设计来做。依赖管理是Maven的的一个重要组成部分，但它的所有远。 Maven是更多的是面向项目的工具，做除了依赖其他几件事情的。这将是值得考虑的，如果你正计划迁移到Maven和使用Maven的附加功能，以及，但它是一个有点多，如果你想使用它的是剥离蚂蚁。

Since what you're wanting to do is add dependency management to an existing Ant project, that's precisely what Ivy's designed to do. Dependency management is a big part of Maven, but far from all of it. Maven is more of a project-oriented tool that does several other things in addition to dependencies. It would be worth considering if you were planning to migrate to Maven and use additional Maven features as well, but it's a bit much if all you'd use it for is to spin off Ant.

您的类型依赖和你的他们的言行举止也将有所作为的期望。拉第三方依赖是在Maven中几乎微不足道，而艾维在重建自己的相关组件的过人之处。在这两种情况下，该工具将不能提供像样的构建，版本和存储库的政策的，那些仍然由你​​，并得到正确的配置需要。

Your type of dependencies and your expectations for how they behave will also make a difference. Pulling third-party dependencies is almost trivial in Maven, while Ivy excels in rebuilding your own dependent components. In either case, the tools won't provide decent build, versioning, and repository policies, those are still up to you and needed to get the configuration right.

这篇关于Maven的常春藤或从蚂蚁管理依赖？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！