|
|
Spring and OSGi |
Cool. Quite an effort to make all of this available. Thanx.
Some more questions:
* Is there any client api that can be used to programmatic use the
bundle repository?
* For the maven case are there available also the maven metadata xmls?
Alin Dreghiciu
On Fri, May 2, 2008 at 10:38 AM, Adrian Colyer
> Direct link to the browse page is here:
> http://www.springsource.com/repository/app/bundle
> Regards, Adrian.
> On 2 May 2008, at 09:16, Alin Dreghiciu wrote:
> Hi Adrian,
> What is "SpringSource repository browser" that is mentioned in the FAQ?
> Is there any way to browse this repository?
> Thanx,
> Alin
> On Thu, May 1, 2008 at 7:25 PM, Adrian Colyer
> <adrian.col...@springsource.com> wrote:
> 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/2008/04/30/introducing-the-springso...).
> 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
> Regards, Adrian.
> Adrian Colyer
> CTO, SpringSource
> http://www.springsource.com
> Registered in England and Wales: No. 5187766 Registered Office: A2
> Yeoman Gate, Yeoman Way, Worthing, West Sussex. BN13 3QZ.
> E-mails should be checked by the recipient to ensure that there are no
> viruses and SpringSource does not accept any responsibility if this is
> not done. Any views or opinions presented are solely those of the
> author and do not necessarily represent those of SpringSource.
> Adrian Colyer
> CTO, SpringSource
> http://www.springsource.com
> Registered in England and Wales: No. 5187766 Registered Office: A2
> Yeoman Gate, Yeoman Way, Worthing, West Sussex. BN13 3QZ.
> E-mails should be checked by the recipient to ensure that there are no
> viruses and SpringSource does not accept any responsibility if this is
> not done. Any views or opinions presented are solely those of the
> author and do not necessarily represent those of SpringSource.