Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

SpringSource bundle repository changing

It appears that SpringSource may be changing the location for hosting of their OSGI bundles?

Our Nexus repository manager has the following repositories defined:

  • External Bundle Releases: http://repository.springsource.com/maven/bundles/external/
  • External Library Releases: http://repository.springsource.com/maven/libraries/external/
  • SpringSource Bundle Releases: http://repository.springsource.com/maven/bundles/release/
  • SpringSource Library Releases: http://repository.springsource.com/maven/libraries/release/

However, when attempting to reference the following dependency, it does not appear to be available from any of these?

<dependency>
    <groupId>org.springframework</groupId>
    <artifactId>org.springframework.jms</artifactId>
    <version>3.2.5.RELEASE</version>
</dependency>

Instead, this appears to be in a new location: http://ebr.springsource.com/repository/app/bundle ??

Hope someone can shed some light on this. Thanks.

like image 223
toolkit Avatar asked Nov 01 '22 21:11

toolkit


1 Answers

In the FAQ of EBR (Enterprise Bundle Repository), the instructions for Maven are to use exactly the settings you are using so you are doing everything right. Also, it's not like repository.springsource.com is moving to ebr.springsource.com, according to the FAQ these two are the same. Or better said, ebr.springsource.com is the web-facing searching tool, while repository.springsource.com is the actual Maven repository.

Related to the discrepancy between what you get from Maven and what you get in web page when searching is that there must be some bug in the web page that makes it not to be synchronized with the actual resources from the Maven repository.

Also, from the same FAQ page you should note that EBR is no longer actively maintained by SpringSource and the bundles in there are no longer up to date.

UPDATE: See this blog post about the decision to freeze EBR and not to publish Spring artifacts as valid OSGi bundles anymore.

Also, the most relevant details about your concern (related to version 3.2.5) are to be found at this forum post where Glyn Normington (committer to various OSGi related projects in SpringSource) specifically says that Spring 3.2.4 is the last version of Spring that will be officially released with valid MANIFEST headers in its artifacts:

After a bit of discussion, we have decided not to publish Spring Framework 3.2.5 bundles to the SpringSource EBR and to keep it read-only.

like image 68
Andrei Stefan Avatar answered Nov 15 '22 06:11

Andrei Stefan