On Sat, 2004-01-17 at 13:16, Mark R. Diggory wrote:
> But...
>
> 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
Mark R. Diggory wrote:
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
/com
But...
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
