How to make Sonatype's Nexus Repository to work with SpringSource’s EBR

3
votes

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.

1
maven-2osginexusspringsource

1 Answers

1
votes

You should be able to add them as proxy repositories (and I suggest turning off indexing). At least it worked for me.