Re: Thoughts on project uniqness.
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 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 >/commons > > or > > /commons-math/ > /commons-collections/ > /xml-apis > ... > > Seems theres some inherent uniqueness that could be enforced simply by > repository structure. Yup, look in the wiki. We've about various formats for the repository and it will be easy to support both new and old formats and we will switch at some point but probably not for 1.0 or 1.1. > -Mark -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Thoughts on project uniqness.
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 /commons or /commons-math/ /commons-collections/ /xml-apis ... This is the type of thing that the Apache Repository project was talking about. I think that they decided to use your 1st example, the fully qualified domain name of the "group". I also like this idea, I've been complaining about the current structure (with the 20 or so commons-* directories) for a while now. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Thoughts on project uniqness.
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 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 /commons or /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]
