Maven的常春藤还是？哪一个是已经在生产系统更好呢？而其他方面的差异？ [英] Maven or Ivy? Which one is better with a system already in production? And the other differences?

问题描述

我知道，这是一个复杂的问题，但我想知道哪一个是在它已经在生产中，用了很多的bug和设计真正坏的制度的情况下更好。一个真正的混乱。

I know that this is a complicated question, but I would like know which one is better in the case of a system that it's already in production, with a lot of bugs and really bad design at all. A really mess.

其实，我问这个，因为我已经转换这个项目Maven和我面临的问题不少。
我需要调整的文件夹结构，独立于公司从该项目做了一个可怕的框架（它被转换成一个罐子LIB），修复了很多，打破了项目的所有时间的详细信息，配置的pom.xml，使一切蚂蚁已经在做，发现真正的应用程序作为自己的版本中使用（该库的重要组成部分改名没有版本号和清单文件是空的）。

Actually, I'm asking this because I'm already converting this project to Maven and I'm facing A LOT of problems. I needed to adjust the folder structure, separate a terrible framework made at the company from the project (it was converted into a jar lib), fix a lot of details that broke the project all the time, configure the POM.xml to make everything that Ant was already doing and discover the libs that are really used in the application as their versions (a big part of the libs was renamed without the version number and the manifest file was empty).

嗯，这是一个真正的地狱。我这个任务，随后我所有的时间是如果我是把它转换为常青藤？会更容易？的问题时都疯狂了。

Well, it was a really hell. I went crazy during this task and the question that followed me all the time was "And if I was converting it to Ivy? Would be easier?".

我从来没有与常春藤工作，但我知道它使用Ant工作，它更容易然后Maven来调整项目。在另一方面，Maven的它更用印花布字（难道我错了吗？），这应该有一个理由！

I never worked with Ivy, but as I know it work with Ant and it's easier then Maven to adapt the project. On the other hand, Maven it's much more used allover the word (Am I wrong?) and this should have a reason!

所以这是我的问题：

• 集成詹金斯/哈德森：常春藤它是那么容易，因为与Maven


• 声纳插件：上述同样的问题。集成起来很简单？


• Eclipse插件：这是Maven的一个非常薄弱的​​点。该插件可怕，但我不知道那些常青藤


• 部署过程中：一旦它的一切配置，部署和使用Maven发布项目它是非常容易。并与艾维？


• 转换：嗯，我在把一个项目，Maven的经验是可怕的，但系统并没有帮助。我有选项是Maven的令人惊异的新项目，项目使用Maven，因为它被创造了，但如果你有一个大的和无组织的项目一个不错的选择。难道我错了吗？


• 插件：它的配置到pom.xml的插件了很多。是否有常春藤这么多的选项？


• 流行：这是上更受欢迎？哪一个更常用的，为什么？

• Integration with Jenkins / Hudson: With Ivy it's so easy as with Maven?
• Sonar plugin: Same question above. The integration it's simple to?
• Plugin for Eclipse: This is a very weak point of Maven. The plugin terrible, but I don't know the Ivy ones.
• Deploy process: Once that it's everything configured, deploy and publish the project with maven it's extremely easy. And with Ivy?
• Conversion: Well, my experience in converting a project to Maven was terrible, but the system didn't helped. The option that I had was that Maven it's amazing to new projects, projects working with Maven since it was created, but not a good choice if you have a big and unorganized project. Am I wrong?
• Plugins: That it's A LOT of plugin to be configured into POM.xml. Is there so many option for Ivy?
• Popularity: Which on is more popular? Which one is more used and why?

嗯，这是这一点。
非常感谢！

Well, it's this. Thanks a lot!

推荐答案

首先，阅读常春藤/ Maven的比较从常春藤网站。关键信息：

First of all, read the Ivy / Maven comparison from the Ivy website. The key information:

首先，最重要的区别是，它们不是在所有相同类型的工具。阿帕奇Maven是一个软件项目管理和COM prehension工具，而阿帕奇常青藤只是一个依赖管理工具，使用Apache Ant™，流行的构建管理工具高度集成。因此，也许更有趣的比较是比较Apache Ant的常春藤+阿帕奇VS Maven的。但是，这超出了这个网页，其中集中在只有依赖管理的范围。

First, the most important difference is that they aren't at all the same kind of tools. Apache Maven is a software project management and comprehension tool, whereas Apache Ivy is only a dependency management tool, highly integrated with Apache Ant™, the popular build management tool. So maybe a more interesting comparison would compare Apache Ant+Ivy vs Apache Maven. But this goes beyond the scope of this page which concentrates on dependency management only.

常春藤增加的依赖管理功能，蚂蚁，所以真的，在什么构建系统使用方面的问题可以是：

Ivy adds dependency management functionality to Ant, so really, the question in terms of what build system you use is either:

• 使用常春藤/蚂蚁


• 迁移到Maven的

如果你的版本是的已的使用Ant，艾维将是一个更容易过渡，因为您的构建脚本并不需要被移植到不同的编译系统。

If your build is already using Ant, Ivy will be an easier transition since your build scripts don't need to be ported to a different build system.

如果您决定过渡到Maven，将需要更多的努力，因为你需要重写你的构建脚本和Mavenize一切以及配置依赖管理。

If you decide to transition to Maven it will require more effort, because you need to rewrite your build scripts and Mavenize everything as well as configure your dependency management.

这也将是更容易从口常青藤/蚂蚁你的依赖管理配置到Maven如果你决定在这个方向去。所以，常春藤依赖管理将是一个很好的敲门砖在长期的去一个Maven配置。

It will also be easier to port your dependency management configuration from Ivy/Ant to Maven if you ever decide to go in that direction. So Ivy dependency management would be a good stepping stone for in the long term for going to a Maven configuration.

这篇关于Maven的常春藤还是？哪一个是已经在生产系统更好呢？而其他方面的差异？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！