Mauro Talevi wrote:
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
No, you missunderstood me, we're not breaking up the repository, its still all one, just organizing it better for management purposes, the directory structure is not different virtual machines.
maven.ibibilio.org/apache/<project> maven.ibibilio.org/codehaus/<project>
same thing as
www.ibibilio.org/maven/apache/<project> www.ibibilio.org/maven/codehaus/<project>
Ultimately the issue here is in organization/group/artifact id's being more hierarchical, not separating out into separate repositories.
-- Mark Diggory Software Developer Harvard MIT Data Center http://www.hmdc.harvard.edu
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
