With this is mind, Jason, how close are we to having "hierarchical" organization/group directories? My point is that it would be far easier for us to control any overlap in projects if the organizations were isolated into separate directories.
for instance
www.ibiblio.org/maven/apache/<project> www.ibiblio.org/maven/codehaus/<project>
also, is it possible to get virtual host names out of Ibiblio, ie
maven.ibiblio.org/apache/<project> maven.ibiblio.org/codehaus/<project>
Maybe this is something we can really push for version two, before there are too many dependent projects?
Mark,
separating maven repositories by organizations sort of defeates the point of putting them in a common unique place such as ibiblio. That is, once could two different url, say dist.apache.org dist.codehaus.org and those can be set on the client side as the maven repos (this is done to access the codehaus.org jars currently)
The nice thing about the maven repository is that it agnostic of
the origin of the artifacts, it just cares about the name of the artifact group, ie the structure underneath ibiblio.org/maven.
That said, one could - for operational/organizational purposes - have different upload areas for different orgs, but then the artifacts themselves should really be put into a single repo.
Cheers, Mauro
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
