As long as we're talking about public Ivy repositories, this is a good opportunity to give a shout-out to the SpringSource Enterprise Bundle Repository: http://www.springsource.com/repository/app/
Do note that the various non-Spring artifacts published on Spring's Ivy repo are not literally the original artifacts but rather OSGi-ified bundles of them. Same JARs+extra metadata. I will say, Ivy RoundUp has its one distinctive approach to being a public Ivy repo--centered around the packager resolver and its own decisions as to Ivy confs--and the SpringSource bundle repo has its own distinctive approach. Neither approach is more valid and neither repo is a be-all-and-end-all, but actually it's nice to know that we're seeing at least the beginnings of a diversity of choices out there for public Ivy repos just as, well, there are for public Maven repos. On Thu, Apr 8, 2010 at 7:41 PM, Archie Cobbs <[email protected]> wrote: > On Thu, Apr 8, 2010 at 11:02 AM, Jeff Evans (IT) < > [email protected]> wrote: > > > > 1) The Maven 2 repository has more than a little crap in it. <snip> > > > > I'll say one more thing about Ivy RoundUp and then shut up... :-) > > The whole point of Ivy RoundUp is to create a *sane* repository with > reliable and precise configuration and dependency information. Right now > there are 231 separate modules and 617 distinct revisions, but there is > always the need for more. > > If people want to be part of the solution (instead of just complaining :-) > please join us. Everyone benefits from the "network effect" of people > contributing ivy.xml files for the modules that they care about and use > every day. In that way it's a project very much in the open source spirit. > > I'll also note that you don't have to use Ivy RoundUp exclusively, as you > can chain it together with other repositories, so it's not an > all-or-nothing > commitment to use it (although of course maven can sometimes make this > difficult too). > > Thanks, > -Archie > > -- > Archie L. Cobbs >
