On 01/09/2007, at 6:22 PM, Stephen Connolly wrote:

Would a better option be to have the repositories store a identifying GUID in their root URL. That way mirrors would pick up the same GUID and be identified as the same repository.

Stephen - did you want to drop this into the user proposals section? I agree we need repository GUIDs and repository metadata, but I think it's a different thing to what I was proposing (apart from naming the directories) so we should track it separately and include all the settings and POM references as well.

Thanks,
Brett


Of course then there's the question, should an aggregating mirror return the GUIDs of all the repositories it aggregates or a unique hash.

My feeling is it should return a unique hash, but maybe it could return information about it aggregating other repositories...

thus:

The repository-id.xml for an aggregate repository could be something like

<repository-id>
 <name>ACME Corp's Aggregated Proxy Repository</name>
 <id>1234-663a-7766-aabbef45-3244</id>
 <aggregate-repositories>
   <id>7688-364a-a7f6-1234567-f56e</id>
   <id>bcd3-5432-8899-9876543-acbd</id>
 </aggregate-repositories>
</repository-id>

While repo1.maven.org could be:

<repository-id>
 <name>Maven Central Repository</name>
 <id>7688-364a-a7f6-1234567-f56e</id>
</repository-id>

And, say java.net2 (http://download.dev.java.net/maven/2) could be

<repository-id>
 <name>Java.net's Maven2 Repository</name>
 <id>bcd3-5432-8899-9876543-acbd</id>
</repository-id>

The advantage I see is that existing clients will not be looking for the repository-id.xml file, so they won't care. If we can't find a repository-id.xml file for the repository, we generate a GUID on the client and store a mapping of URLs to GUIDs in a file in ~/.m2/ so that a user can control the mapping of these autogenerated GUIDs

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to