Archiva 与 Nexus 相比如何？
已经有一些类似的问题了，但大多数要么集中在 Nexus 与 Artifactory 上，要么已经有几年了。
我想了解一下这两个项目目前的情况。我的印象是 Nexus 是最受推崇的存储库管理器，但我确实倾向于（稍微）更喜欢纯粹的免费项目（嘿，一点意识形态不会伤害任何人）。
我的用例非常简单：我只想要一个按需依赖项缓存，其中包含六个我们自己的工件。我将把它与 Ivy（不是 Maven）一起使用，我们不进行自动化构建，并且只有几个开发人员使用它。所以我也想知道 Nexus 的更高级功能是否是我不需要的东西。
在做出选择之前我应该注意什么？
There are a few similar questions already, but most are either focused on Nexus vs. Artifactory, or are a few years old.
I wanted to get a sense of where the two project stand these days. My impression is that Nexus is the best regarded repository manager, but I do tend to (slightly) prefer purely Free projects (hey, a little ideology never hurt anyone).
My use-case is pretty simple: I just want an on-demand dependency cache, with half a dozen of our own artifacts. I'll be using it with Ivy (not Maven), we don't do automated builds, and it will only be a couple of developers using it. So I'm also wondering if Nexus' more advanced features are something I won't need anyway.
Anything I should be aware of before making the choice?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（7）
声明偏见：我是 Archiva 项目的创始人。
我可以向您保证，Archiva 以及实际上所有 3 个项目都将满足您列出的需求，并且所有项目都具有一些更高级的功能，随着您的环境的进步，您可能会发现这些功能很有用。它们都可以很快尝试，因此您可以看到什么对您来说最自然。
正如您所指出的，Archiva 是最宽松的许可，并且在 Apache 并不与特定的公司利益相关（如果这对您很重要的话）。
关于 Ivy，我们最近有人自愿为 Ivy 格式存储库编写本机支持，如果成功的话您可能会感兴趣。
Declaring bias: I'm the founder of the Archiva project.
I can assure you Archiva, and indeed all 3 projects, will satisfy the needs you've listed, and all have several more advanced features that you'll likely find useful as your environment progresses. They're all quick to try, so you can see what feels most natural for you.
As you've noted, Archiva is the most permissively licensed, and being at Apache is not tied to a particular corporate interest, if that's important to you.
With regard to Ivy, we have someone recently volunteering to write native support for Ivy-format repositories, which you might be interested in if it pans out.
我首先使用了 Apache Archiva，并且对它非常满意，因为它满足了我们公司的需求。好吧，我在 Debian 64 位机器上安装它时遇到了一些小问题，但没什么严重的。
但过了一段时间，我尝试了 Nexus，我真的被它漂亮、闪亮的用户界面迷住了。好吧，有时它有点超载，但最终我还是在公司里运行 Nexus。但从功能角度来看，两者都可以使用。
I have used Apache Archiva in the first place and I was pretty happy with it, because it fulfilled the needs we had in the company. OK, I had some little problems with installing it on my Debian 64bit machine, but nothing serious.
But after a while I tried Nexus and I was really blended by the nice and shiny user interface. OK, sometimes it's little bit overloaded, but in the end I ended up with running Nexus in the company. But from the functional point of view, you can use both.
我们在公司使用 Nexus Professional，我们对此非常满意。我们确实将其用于自动化构建，并利用了许多高级功能。我同意你的观点，免费版本可能会很好地满足你的需求。
我没有任何使用 Archiva 的经验，但我确信这也是一个合适的选择。
We use Nexus Professional at my company and we have been very happy with it. We do use it for automated builds, and take advantage of a lot of the advanced features. I agree with you that the free version will probably fulfill your needs fine.
I don't have any experience with Archiva, but I am sure that would be a suitable choice as well.
我刚刚开始将 Nexus 与 ivy 一起使用。我只想使用 nexus 仅使用所需的工件填充项目存储库（没有传递 deps 的 ivy 和代理模式下的 nexus 中央存储库）。因此，当添加新的依赖项时，我可以通过 Nexus 将构建切换到中央存储库，它将填充我的项目存储库，并且构建过程中的下一个开发人员可以直接使用项目存储库（因此项目存储库将仅包含所需的工件，而不会导致我以前的项目出现问题的混淆库） ）。
Nexus 看起来比 Artifactory 更好，因为它使用文件系统而不是数据库来保存存储库。
关于 nexus 与 apache archiva 我的快速测试表明，nexus 更直观，而且速度更快。
I'm just starting using nexus with ivy. I want to use nexus only to populate project repository with only required artifacts (ivy without transitive deps and nexus central repo in proxy mode). So when adding new dependency I can switch build to central repo via nexus, it will populate my project repository and next developers during building can use project repository directly (thus project repository will contain only required artifacts without confusing libraries which caused problems in my previous projects).
Nexus looks better choice than Artifactory because of using filesystem instead of database to keep repository.
About nexus vs apache archiva my quick tests show that nexus is more intuitive and is as well a bit faster.
Archiva 有很多 bug，如果你只按照官方指南进行配置，它永远不会工作（http://archiva.apache.org/docs/1.3.6/quick-start.html）。你必须通过猜测来配置它。
Nexus 比 Archiva 更容易，但比 Archiva 丑陋。
例如，我的操作系统是Windows 2003，Archiva 1.3.4、1.3.6、1.4，Archiva可以下载log4j.jar、junit.jar，但它永远不会下载javax\jms\jms\1.1\jms-1.1.jar。
不要使用Archiva，它太难用了。 Nexus 非常简单。
Archiva has many bugs, it never works if you only config it follow the offical guide(http://archiva.apache.org/docs/1.3.6/quick-start.html). You have to config it by guess.
Nexus is more easy than Archiva, but is ugly then Archiva.
For example, My OS is Windows 2003, Archiva 1.3.4, 1.3.6, 1.4, Archiva can download log4j.jar, junit.jar, but it never download javax\jms\jms\1.1\jms-1.1.jar.
Do not use Archiva, it is too hard to use. Nexus is very easy.
您可以检查此页面以了解 archiva 与 nexus 与artifactory 的比较 https://binary-repositories-comparison.github .io/
You cana check this page for archiva vs nexus vs artifactory comparison https://binary-repositories-comparison.github.io/
有 Artifactory 与 Nexus 与 Archiva 和 ProGet 等其他工具的比较
https： //www.itcentralstation.com/products/comparisons/archiva_vs_jfrog-artifactory_vs_sonatype-nexus-repository
https://www.praqma.com/stories/artifactory-nexus-proget/
，但第一个是 2018 年的，看来 Nexus 获得了更多选票。
SO 上也有非常好的实时细节讨论和有价值的数据
我们应该使用 Nexus 还是 Artifactory 作为 Maven 存储库？
There are comparisons of Artifactory vs Nexus vs other tools like Archiva and ProGet
https://www.itcentralstation.com/products/comparisons/archiva_vs_jfrog-artifactory_vs_sonatype-nexus-repository
https://www.praqma.com/stories/artifactory-nexus-proget/
and yet the 1st one is of 2018, it seems that Nexus gets more votes.
There's very good live detail discussion and valuable data at SO, too
Should we use Nexus or Artifactory for a Maven Repo?