如何使 Sonatype 的 Nexus 存储库与 SpringSource 的 EBR 配合使用
我希望添加 SpringSource EBR（企业捆绑存储库：http://www.springsource.com/repository/) 到 Nexus 作为代理。我这样做的主要原因是 SpringSource OSGi 化了各种众所周知的 OSS 项目（例如：Velocity、AspectJ...），使它们很容易包含在 OSGi 运行时中。
不管怎样，Nexus 如何“查看”EBR 似乎存在一些问题，因为即使我可以远程浏览存储库，它也根本没有被代理和正确索引。 作为一个提示，我观察到 Nexus 没有看到其他 Maven 存储库（例如：Central、google...）公开的直接 Maven 组（例如：org/...），而是一个单独的外部远程导航时插入 或 release 文件夹/根目录。
以下是我感兴趣的 SpringSource EBR 存储库：
<预><代码><存储库>;com.springsource.repository.bundles.release SpringSource Enterprise Bundle Repository - SpringSource Bundle Releases http://repository.springsource.com/maven/bundles/release <存储库>com.springsource.repository.bundles.external <名称>SpringSource Enterprise Bundle 存储库 - 外部捆绑版本http://repository.springsource.com/maven/bundles/external
如果这个存储库直接指定到 Maven 项目 pom.xml 中，一切都很好，但不是通过 Nexus。
I'm looking to add the SpringSource EBR (Enterprise Bundle Repository: http://www.springsource.com/repository/) to Nexus as a proxy. My main reason to doing so is that SpringSource OSGi-fied various well known OSS projects (ex: Velocity, AspectJ...), making them easy to be included in OSGi runtimes.
Anyway, it seams that are some troubles with how Nexus "see" EBR since even that I can browse remotely the repository, it's not proxi-ed and correctly indexed at all.
As a hint what I observed is that Nexus doesn't see the direct maven groups (ex: org/...) as exposed by other Maven repositories (ex: Central, google...) but instead a separate external or release folder/root is inserted when navigating remotely.
Bellow are the SpringSource EBR repositories of my interest:
<repository> <id>com.springsource.repository.bundles.release</id> <name>SpringSource Enterprise Bundle Repository - SpringSource Bundle Releases</name> <url>http://repository.springsource.com/maven/bundles/release</url> </repository> <repository> <id>com.springsource.repository.bundles.external</id> <name>SpringSource Enterprise Bundle Repository - External Bundle Releases</name> <url>http://repository.springsource.com/maven/bundles/external</url> </repository>
If this repositories are specified directly into a Maven project pom.xml everything is just fine, but not through Nexus.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您应该能够将它们添加为代理存储库（我建议关闭索引）。至少它对我有用。
You should be able to add them as proxy repositories (and I suggest turning off indexing). At least it worked for me.