java Archiva 与 Nexus 相比如何?

声明:本页面是StackOverFlow热门问题的中英对照翻译,遵循CC BY-SA 4.0协议,如果您需要使用它,必须同样遵循CC BY-SA许可,注明原文地址和作者信息,同时你必须将它归于原作者(不是我):StackOverFlow 原文地址: http://stackoverflow.com/questions/5587237/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me): StackOverFlow

提示:将鼠标放在中文语句上可以显示对应的英文。显示中英文
时间:2020-10-30 11:47:51  来源:igfitidea点击:

How does Archiva compare to Nexus?

javamavenivynexusarchiva

提问by Dmitri

There are a few similar questions already, but most are either focused on Nexus vs. Artifactory, or are a few years old.

已经有一些类似的问题,但大多数要么集中在 Nexus 与 Artifactory 上,要么已经有几年了。

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 littleideology never hurt anyone).

我想了解这两个项目最近的情况。我的印象是 Nexus 是最受推崇的存储库管理器,但我确实倾向于(稍微)更喜欢纯粹的免费项目(嘿,一点意识形态永远不会伤害任何人)。

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.

我的用例非常简单:我只想要一个按需依赖缓存,有六个我们自己的工件。我将与 Ivy(不是 Maven)一起使用它,我们不进行自动构建,并且只有几个开发人员使用它。所以我也想知道 Nexus 更高级的功能是否是我不需要的东西。

Anything I should be aware of before making the choice?

在做出选择之前,我应该注意什么?

回答by Brett Porter

Declaring bias: I'm the founder of the Archiva project.

声明偏见:我是 Archiva 项目的创始人。

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.

我可以向您保证,Archiva 以及所有 3 个项目都将满足您列出的需求,并且所有项目都具有一些更高级的功能,随着环境的发展,您可能会发现这些功能很有用。他们都很快就会尝试,所以你可以看到什么对你来说最自然。

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.

正如您所指出的,Archiva 是许可最宽松的,并且在 Apache 工作与特定的公司利益无关,如果这对您很重要的话。

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.

关于常春藤,我们最近有人自愿为常春藤格式的存储库编写原生支持,如果它成功,你可能会感兴趣。

回答by H6.

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.

我首先使用了 Apache Archiva,我对它非常满意,因为它满足了我们公司的需求。好的,我在我的 Debian 64 位机器上安装它时遇到了一些小问题,但并不严重。

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,我真的被漂亮而闪亮的用户界面所融合。好吧,有时它有点超载,但最后我最终在公司运行 Nexus。但是从功能的角度来看,您可以同时使用两者。

回答by dbyrne

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.

我们在我的公司使用 Nexus Professional,我们对此非常满意。我们确实将它用于自动构建,并利用了许多高级功能。我同意您的看法,免费版本可能会很好地满足您的需求。

I don't have any experience with Archiva, but I am sure that would be a suitable choice as well.

我对 Archiva 没有任何经验,但我相信这也是一个合适的选择。

回答by kodstark

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。我只想使用 nexus 来填充仅包含所需工件的项目存储库(ivy 没有传递 deps 和代理模式下的 nexus 中央存储库)。因此,在添加新依赖项时,我可以通过 nexus 将构建切换到中央存储库,它将填充我的项目存储库,构建期间的下一个开发人员可以直接使用项目存储库(因此,项目存储库将仅包含所需的工件,而不会混淆导致我以前项目中出现问题的库) )。

Nexus looks better choice than Artifactory because of using filesystem instead of database to keep repository.

Nexus 看起来比 Artifactory 更好,因为它使用文件系统而不是数据库来保存存储库。

About nexus vs apache archiva my quick tests show that nexus is more intuitive and is as well a bit faster.

关于 nexus 与 apache 存档,我的快速测试表明 nexus 更直观,速度也更快一些。

回答by light

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.

Archiva 有很多错误,如果您只按照官方指南(http://archiva.apache.org/docs/1.3.6/quick-start.html)对其进行配置,则它永远不会工作。你必须通过猜测来配置它。

Nexus is more easy than Archiva, but is ugly then Archiva.

Nexus 比 Archiva 更容易,但比 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.

例如,我的操作系统是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。

Do not use Archiva, it is too hard to use. Nexus is very easy.

不要使用Archiva,它太难用了。Nexus 非常简单。

回答by Marek Duciuc

You cana check this page for archiva vs nexus vs artifactory comparison https://binary-repositories-comparison.github.io/

您可以查看此页面以了解档案、关系和人工制品的比较https://binary-repositories-comparison.github.io/