通过 Nexus Repository Manager 访问 JBoss 和其他存储库时出现问题
我们使用 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 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
根据这篇博客文章
http://www.sonatype.com/people/2011/09 /8942/
您不再需要担心引用 JBoss 存储库，因为所有 JBoss 工件都已清理并迁移到 Maven Central。
Java.net 过去并不可靠并且存在问题，这也会导致同样的问题。现在应该好多了，因为它也可以在 Nexus 上运行。
According to this blog post
http://www.sonatype.com/people/2011/09/8942/
you no longer need to worry about having the JBoss repo referenced because all JBoss artifacts have been cleaned up and migrated to Maven Central.
Java.net used to be unreliable and had issues, which would cause the same issue. Should be much better now since it runs on Nexus as well.