With the possibility that multiple remote maven repositories can exist and projects can be published that have the same project names to different remote repositories, it seems there would really be issues with name clashes eventually here?
Seems that there should be some effort to make sure that projects maintain uniqueness. Usually namespacing (using host domains) is used to accomplish this (like in xml for instance). Is there any effort to do this in maven repositories.
Looking in the ibiblio repository, it seems there's going to eventually be political issues with the whole apache commons, jakarta commons, xml commons for instance if all jakarta commons projects have project names "commons-*".
This is where nested directory structures come into play. Which is easier to maintain uniqueness?
/jakarta.apache.org/commons/... /xml.apache.org/commons/... /commons.apache.org/...
or
/org
/apache
/jakarta
/commons
/xml
/commons
/commonsor
/commons-math/ /commons-collections/ /xml-apis ...
Seems theres some inherent uniqueness that could be enforced simply by repository structure.
-Mark
-- Mark Diggory Software Developer Harvard MIT Data Center http://osprey.hmdc.harvard.edu
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
