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-springsource-application-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.
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.
> 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-springsource-application-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.
> 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.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.
> 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.
Absolutely. Just go to the repository website (http:// www.springsource.com/repository/) and click on the "browse by bundle" link on the left-hand side.
> 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- >> springsource-application-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.
>> 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.
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.
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?
<adrian.col...@springsource.com> wrote: > Absolutely. Just go to the repository website > (http://www.springsource.com/repository/) and click on the "browse by > bundle" link on the left-hand side.
> 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.
> 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.
> 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.
> 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?
> On Fri, May 2, 2008 at 10:38 AM, Adrian Colyer > <adrian.col...@springsource.com> wrote: > > Absolutely. Just go to the repository website > > (http://www.springsource.com/repository/) and click on the "browse by > > bundle" link on the left-hand side.
> > 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:
> > 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.
> > 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.
> > 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.
I know that can be used with maven but maven as I recall can work even without the metadata (not very sure about that) so I'm wondering if the "maven-metadata.xml" files are present.
On Fri, May 2, 2008 at 10:56 AM, Stuart McCulloch <mccu...@gmail.com> wrote: > 2008/5/2 Alin Dreghiciu <adreghi...@gmail.com>:
> > 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?
> thanks again for doing this - as Alin says, must have taken a lot of effort
> > Alin Dreghiciu
> > On Fri, May 2, 2008 at 10:38 AM, Adrian Colyer
> > <adrian.col...@springsource.com> wrote: > > > Absolutely. Just go to the repository website > > > (http://www.springsource.com/repository/) and click on the "browse by > > > bundle" link on the left-hand side.
> > > 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:
> > > 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.
> > > 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.
> > > 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.col...@springsource.com> wrote: > Absolutely. Just go to the repository website > (http://www.springsource.com/repository/) and click on the "browse by > bundle" link on the left-hand side.
> 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.
> 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.
> 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.
> I know that can be used with maven but maven as I recall can work even > without the metadata (not very sure about that) so I'm wondering if > the "maven-metadata.xml" files are present.
> On Fri, May 2, 2008 at 10:56 AM, Stuart McCulloch <mccu...@gmail.com> > wrote: > > 2008/5/2 Alin Dreghiciu <adreghi...@gmail.com>:
> > > 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?
> > thanks again for doing this - as Alin says, must have taken a lot of > effort
> > > Alin Dreghiciu
> > > On Fri, May 2, 2008 at 10:38 AM, Adrian Colyer
> > > <adrian.col...@springsource.com> wrote: > > > > Absolutely. Just go to the repository website > > > > (http://www.springsource.com/repository/) and click on the "browse > by > > > > bundle" link on the left-hand side.
> > > > 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.
> > > > 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.
> > > > 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.
>> thanks again for doing this - as Alin says, must have taken a lot >> of effort
It was pretty intense, yes :) Getting all of the versioning information correct, and then making sure that everything in the repository was self-consistent took a lot of time and attention to detail. Our initial estimate was that we'd need to do about 150 jars, but we ended up doing almost 300 because of the transitive dependencies. The exercise taught us a lot about the rats-nest of inter-dependencies between enterprise libraries!!
What may not have been obvious from my previous post is that you can also use the online browser to get a full report on the transitive mandatory and optional dependency set of any bundle (so you know what you need to download and install). In a future version of the application we'll look at providing a single download link to pull down an archive containing the whole set.
You'll see that at a minimum you need to have Apache Commons Logging and Spring Core in order to use Spring Beans. This is the transitive dependency set, so just those three jars should be all you need.
If you expand the section underneath, "Full Dependencies" you'll find all the additional bundles you may want to install in order to satisfy optional dependencies of Spring Core or the bundles that Spring Core depends on.
Finally at the bottom the "unresolved dependencies" shows import- package statements in the transitive dependency set that cannot be satisfied by bundles in the repository. According to the rules of the repository, you should only ever see optional imports in this section, and indeed this is the case here.
There's a JIRA here: http://issuetracker.springsource.com/secure/ CreateIssue!default.jspa where you can raise requests for additional libraries to be included. If the 300 we've already got don't include something you need!
> * Is there any client api that can be used to programmatic use the > bundle repository?
We don't yet have a client API, but we're working on making one available very soon. The plan is to hook the repository up to the Application Platform tools (see the last section of my post here: http://blog.springsource.com/main/2008/05/01/completing-the-picture- spring-osgi-and-the-springsource-application-platform/) so that you can search for, download, and install bundles directly from the IDE.
> 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?
> thanks again for doing this - as Alin says, must have taken a lot > of effort
> Alin Dreghiciu
> On Fri, May 2, 2008 at 10:38 AM, Adrian Colyer > <adrian.col...@springsource.com> wrote: > > Absolutely. Just go to the repository website > > (http://www.springsource.com/repository/) and click on the > "browse by > > bundle" link on the left-hand side.
> > 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- > springsource-application-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.
> > 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.
> > 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.
Registered in England and Wales: No. 5187766 Registered Office: A2 Yeoman Gate, Yeoman Way, Worthing, West Sussex. BN13 3QZ.
This e-mail and any attachments transmitted with it are strictly confidential and intended solely for the person or entity to whom they are addressed. Unauthorised use, copying, disclosure or distribution is prohibited. If you receive this e-mail in error please notify the sender immediately and then delete it along with any attachments. 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.
|
