Hi, Am Dienstag, den 27.05.2008, 22:56 +1200 schrieb Mark Derricutt: > Just noticed this post - this is one of things that really annoyed the hell > out of me when I first started using Ivy as a dependency manager 2-3 years > ago - Ivy kept its ivy.xml files in its own repository that pointed to the > ibiblio based maven repository. The problem I found with this is that > either ibiblio would go down, or the ivy repository would be down, or one or > the other would delete or move artifacts around.
Nowadays the central maven repository - repo1.maven.org - is not run by ibiblio any more but by Apache itself, AFAIK. And to me repo1.maven.org seems far more reliable than the former ibiblio repo. The repository.xml is just an XML file whish is provided through a normal HTTP server (from felix.apache.org in my proposal). See http://oscar-osgi.sourceforge.net/obr2/repository.xml. This file lists the bundles available as well as their capabilities and requirements. The actual bundles are referred to by the repository.uri attribute. So I think, this is not so much of a problem. Regards Felix > I found this soon led to inconsistencies in the repositories - and > dependencies on multiple upstream providers - chasing down either ivy > maintainers, maven maintainers, plus the project maintainers seemed like a > recipe for disaster which led to maintaining an internal private repository > for everything. > > Hopefully the OBR repository could avoid possible issues like this. > > Mark > > On Tue, May 27, 2008 at 10:43 PM, Felix Meschberger <[EMAIL PROTECTED]> > wrote: > > > But my point is that we do NOT replicate the actual bundle files but > > keep the in the Maven Repository, where they already are. We just create > > repository.xml files that refer to the existing bundles in the Maven > > Repository. > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
