OSGi Bundle Repository available for Enterprise Libraries
# posting Adrian's email announcement:
Some of you may have seen the recent announcement of the SpringSource Application Platform (if not, a good starting point is Rob Harrop's blog here: http://blog.springsource.com/main/20...tion-platform/). The platform uses Spring and Spring Dynamic Modules as the end-user programming model, and contains a lot of smarts to make that model work smoothly with existing enterprise libraries.
Regardless of whether or not you choose to use the Platform, subscribers to this list will almost certainly be interested in the SpringSource Bundle Repository (http://www.springsource.com/repository). To support the development of enterprise applications with OSGi we've created a repository with nearly 300 of the most commonly used enterprise libraries when developing Spring applications. (Yes, this was a big and very resource intensive undertaking!) Every bundle in the repository has full OSGi manifests, and before any artefact gets into the repository it is verified in a running OSGi Service Platform to ensure it loads and resolves correctly.
The repository meets the following criteria:
* Every jar file in the repository is a valid OSGi bundle. Any jar you download from the repository can be deployed as-is into an OSGi Service Platform. It can also be used as a regular jar file outside of OSGi.
* Every bundle and library has full version information associated with it. The package export information for a bundle contains version information, and the package import information for a bundle contains full version range compatibility information.
* The repository is transitively complete. The mandatory dependencies of any bundle are guaranteed to also be in the repository. Most of the optional dependencies of any bundle in the repository will also be present. The bundles listed in any library definition are guaranteed to be in the repository.
* The repository is self-consistent. Before any artefact is uploaded to the repository, we verify that it can be installed, resolved, and started in an OSGi Service Platform (using the same profile as the SpringSource Application Platform) alongside all of the other bundles in the repository. * The repository can be used from Ivy and Maven based builds.
There is an FAQ here for those who are interested in further details http://www.springsource.com/repository/app/faq
The original email can be seen at:
Related information is available at:
Spring repository incompatible with IVY 1.4.1 for some bundles
I'm having quite a few issues with this repository when using IVY 1.4.1
Originally Posted by Costin Leau
What seems to happen on some bundles is that when a binary JAR file is requested as a dep, IVY actually pulls down a jar full of source code. Examples are:
<dependency org="org.springframework" name="org.springframework.context" rev="2.5.4.A" />
<dependency org="org.apache.log4j" name="com.springsource.org.apache.log4j" rev="1.2.15" />
<dependency org="org.hibernate" name="com.springsource.org.hibernate.annotations" rev="3.3.0.ga" />
This all works fine using IVY 2 beta. Not sure if this is the best place to report this problem but it's worth pointing out that the link to report a problem on the repository pages is broken too.
This is more or less a cross post from the core forum but I thought on reflection this was a better place to post.
Source code for the bundle repository
There are a few libraries in the spring source enterprise bundle repository that are one or two minor revisions older than versions that I use.
I would like to create bundles for these newer versions, and an easy starting point would be the existing pom.xml files for the versions in the bundle repository.
Is there anonymous svn access to these files ?
Cannot access EBR with maven to build greenpages example.
I am just starting out with the greenpages example to learn about the dmserver and I have noticed that the access for maven into the enterprise bundles repository does not seem to work. I found this post from a couple of days ago and was wondering if there was some feedback on the subject or if there was somewhere else more appropriate to explore this access issue?
Originally Posted by frederic.conrotte