Fantastic idea!
~ Dave Smiley
On 2006-05-17 21:21:59 -0400, Brad Davis <[EMAIL PROTECTED]> said:
It strikes me that centralized repositories, even with mirrors is a
potential scalability problem and point of failure. Its also a point
of failure since the more projects use Maven, the more administration
has to be done to allow Project X, Y, or Z access to publish updates to
the repo.
Why not leverage DNS to allow projects to publish to project specific
repositories? This would require that the group ID be convertible into
some sort of DNS resolvable name in a consistent manner, but that's
nearly the case for many projects already. Here's how it would work...
As a client, Maven could look at the group ID of say
org.apache.maven.plugins. It could do DNS TXT record lookups on
plugins.maven.apahche.org, then maven.apache.org and then apache.org
looking for repository information (encoded via some convention in the
TXT record). The centralized repository structure could continue to be
used as a fallback for projects whose group ID can't conform to a DNS
resolvable address, or who don't have control over their DNS servers at
that level.
As a project owner, once the DNS support is there, publishing a new
version of my artifcats to Maven no longer requires coordination with
another party. In fact, publishing to Central changes from a push
model to a pull model. A one time agreement to publish items from a
given group ID means that the central server can now monitor for
changes on the project specific repositories.
My 2 cents.
Brad
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
