通过 Nexus Repository Manager 访问 JBoss Repository 时出现问题
我们使用 Nexus Repository Manager 作为我们的企业存储库管理器。 nexus 存储库管理器通过以下远程 URL 链接到 JBoss 存储库。
当您的防火墙不允许您访问 JBoss url 时，通常会出现此消息。但是nexus能够访问maven中央仓库，这间接说明Proxy没有问题。
以下网址也会显示相同的消息
名称 URL 类型/策略
java.net - Maven 2 (http://download.java.net/maven/2/) 代理/发布
java.net-m1 (http://download.java.net/maven/1/) 代理/发布
Apache Snapshots (http://repository.apache.org/snapshots/) proxy/Snapshot
如果有人对此有任何想法，请回复。
We are using Nexus Repository Manager as our Corporate Repository Manager.
The nexus repository manager was linked to JBoss Repository with following remote url.
https://repository.jboss.org/nexus/content/repositories/releases/
Today when I checked the nexus, i saw following message for JBoss
In Service - Remote automatically blocked and unavailable.
This message generally comes when your firewall is not allowing you to access the JBoss url. But the nexus is able to access maven central repository, which indirectly tells that there is no problem in the Proxy.
The same message is also shown for following urls
Name URL Type/Policy
java.net - Maven 2 (http://download.java.net/maven/2/) proxy/Release
java.net-m1 (http://download.java.net/maven/1/) proxy/Release
Apache Snapshots (http://repository.apache.org/snapshots/) proxy/Snapshot
Please reply if any one has idea about it.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Maven Central 没有重新定位，只是有一些新的方法来防止存储库“抓取”。如果 maven 使用绝对路径请求，它仍然会提供工件。因此，对于 Maven Central，您应该使用 URL http://repo1.maven.org/maven2/ 因为它是唯一一个有效的。正如您所指出的，search.maven.org（其中抓取工具被重定向）是完全不同的野兽，不能与 Maven 或 Nexus 一起用作远程存储库。
您应该检查为什么您的 Nexus 认为 Maven Central 无法访问。您在运行 Nexus 的主机和外部世界（互联网）之间是否有一些内部（可能是透明的）HTTP 代理？或者有其他方法阻止 Nexus 伸出援手？另外，也可能是网络问题（断电、断电）......并且 Nexus 只是阻止代理以防止连接泄漏。
Maven Central is NOT relocated, only has some new means preventing repository "scraping". It will still serve up artifacts if requested by maven using absolute paths. So, for Maven Central, you should use the URL http://repo1.maven.org/maven2/ as it's the only one working. As you noted, the search.maven.org (where scrapers are redirected) is totally different beast, not usable with Maven nor Nexus as remote repository.
You should rather check why your Nexus thought Maven Central is not reachable. Do you have some internal (maybe transparent) HTTP Proxy between host running Nexus and outer world (Internet)? Or some other means preventing Nexus reaching out? Also, it might be network issue (brownout, blackout) of the network.... and Nexus just blocked proxying to prevent connection leaks.
检查以下项目：
Check the following items: