简体繁体 English

Nexus 3代理到虚拟Maven 2存储库

[英]Nexus 3 Proxy to virtual maven 2 repository

原文 2017-09-11 16:12:24 9 1 java/ maven/ nexus

We moved from Nexus 2 to Nexus 3 and face the problem of still need to support some artifacts uploaded by projects still working with Maven 1. 我们从Nexus 2迁移到Nexus 3，并面临仍然需要支持仍在使用Maven 1的项目上传的某些工件的问题。

In Nexus 2 I was able to setup a Maven 1 repository ( N2-P-M1 ) and I configured a virtual Maven 2 repository ( N2-V-M2 ) by which it was able to download the artifacts from a Maven 2 project. 在Nexus 2中，我能够设置Maven 1存储库（ N2-P-M1 ），并且配置了虚拟Maven 2存储库（ N2-V-M2 ），通过它它可以从Maven 2项目中下载工件。

Now with Nexus 3 there is no native support for Maven 1 repositories. Nexus 3现在不支持Maven 1存储库。 So I kept the Nexus 2 running and configured a Maven 2 proxy repository in Nexus 3 ( N3-P-M2 ) that is meant to be a proxy for the virtual repository in Nexus 2. 因此，我保持了Nexus 2的运行，并在Nexus 3（ N3-P-M2 ）中配置了一个Maven 2代理存储库，该代理存储库旨在作为Nexus 2中虚拟存储库的代理。

But unfortunately I see no assets in Nexus 3 for that proxy (N3-P-M2). 但是很遗憾，我在Nexus 3中看不到该代理（N3-P-M2）的资产。

I observed that when browsing the virtual Maven 2 repository in Nexus 2 there are only JARs and POMs but no metadata files. 我观察到，在Nexus 2中浏览虚拟Maven 2存储库时，只有JAR和POM，但是没有元数据文件。 This may be a problem for Nexus 3 I suppose. 我想这可能是Nexus 3的问题。

1 个解决方案

You might try setting the Layout Policy to permissive instead of strict, if you haven't already on the Nexus Repo 3 side. 如果您尚未在Nexus Repo 3方面，可以尝试将布局策略设置为宽松而非严格。 That will allow pretty much any path to pass through. 这将允许几乎所有路径通过。 I'm not sure if that's the problem, but it might be worth trying it out. 我不确定这是否是问题，但可能值得尝试。

Shy of that working, please file an issue with us at our JIRA: https://issues.sonatype.org/browse/NEXUS . 避开该工作，请通过JIRA向我们提出问题： https : //issues.sonatype.org/browse/NEXUS 。 Since you are proxying what SHOULD be a Maven 2 repository, I'd like to know personally what the issue is. 由于您代理的应该是Maven 2存储库，因此我想亲自了解问题所在。