Hi all, Thanks for your feed-back on the repository feature. We did consider the direct usage of the central Maven repository but had several concerns:
- some Restlet artifacts rely on third-party dependencies that are not available in the central Maven repository either. We wanted a way to provide them transparently. - Maven central repository has two ways to upload artifacts, one is manual (unpractical) and the other relies on the rsync/ssh protocol, which looks too intrusive for us. If they had an HTTP-based synchronization mechanism, we would be happy to have them sync with our public repository. - we needed our own repository (http://maven.noelios.com) in order to provide support for Noelios customers, providing them custom builds for example, controlling the freshness of artifacts, potentially proposing commercial products in the future. IMHO, the concept of a central storage point (even mirrored) seems like a good idea at the first thought but will hardly scale in the long term. All the JAR files on earth won't fit into a single repository or won't be well synchronized. For example, we rely on FreeMarker 2.3.10 but its artifacts haven't been updated yet on Ibiblio... There has to be a better distributed way to deal with this. Maybe the central repository should be a meta-repository instead of a central storage point, or both. Many organizations already rely on internal Maven repositories that sync with several external and internal ones. Adding an external one for them is very easy, and ensures that all the artifacts are downloaded once and reused internally. Some interesting related projects: http://maven-proxy.codehaus.org/ http://proximity.abstracthorizon.org/about-proximity.html I hope this helps to clarify our choice. Best regards, Jerome > -----Message d'origine----- > De : Valdis Rigdon [mailto:[EMAIL PROTECTED] > Envoyé : vendredi 4 mai 2007 02:20 > À : [email protected] > Objet : RE: Maven Repository available > > From someone who is currently moving from Ant build scripts to Maven2, > having the jars and dependencies in ibiblio would be a better > solution. > > > Valdis > > > > > I'll (strongly) second these sentiments. > > > > --Chuck > > > > ________________________________ > > > > From: Mark Reynolds [mailto:[EMAIL PROTECTED] > > Sent: Thursday, May 03, 2007 2:44 PM > > To: [email protected] > > Subject: Re: Maven Repository available > > > > > > Thanks for doing this. It is a huge step in the right > direction. I only > > wish you hadn't decided to create your own release repository, and > > instead would use the maven central repository. Perhaps you > may consider > > this for the next level of making things easy for your users. > > > > In my project, I have many dependencies. If each project > set up their > > own repository, I would have a huge repository section in my pom and > > each repository would have to be checked for each artifact. > Moreover, > > there are many mirrors of the central repository so there > isn't a single > > point of failure for retrieving an artifact, whereas it is > unlikely that > > each individual project will be able to provide mirroring, > and even if > > they did, I would have to manage referencing all those mirrors. > > > > I know many projects have set up an automatic syncing with with the > > central repository, so that they don't have to do any extra > work (after > > the syncing is set up) to publish releases to the central repo. > > > > Again, I am most appreciative of what you have done. I just > hope it is > > not a part of a trend for everyone to set up their own release > > repositories (and yes, restlet is not the only one but > thankfully they > > are still few in number). > > > > -- Mark R > > > > > > On 5/3/07, Thierry Boileau <[EMAIL PROTECTED]> wrote: > > > > **Hello all, > > > > One the most frequent enhancement request that we received was > > to > > improve our support for Apache Maven <maven.apache.org> > > technology. We > > initially responded by shipping some Maven POM files within our > > Restlet > > distribution. This enabled users to upload those JAR files to a > > local > > Maven repository, using a script like the one available in our > > Wiki. > > > > But, this was clearly not easy enough and forced users to > > download the > > full distribution for each new version released, instead of just > > updating a couple of JARs. We also had issues with some > > third-party > > dependencies which aren't available in public Maven > > repositories, like > > the db4o, AsyncWeb or Simple. > > > > We listened to your feed-back and decided to launch dedicated > > Maven > > repository. It is freely accessible from > > http://maven.restlet.org and > > contains all Restlet JARs and third party dependencies that > > aren't > > available in the main public Maven repository. It will be > > automatically > > refreshed on the 1st and on the 15th of each month. > > > > Best regards, > > Thierry Boileau > > > > > >
