> On Mon, 2003-03-03 at 19:54, Stanley,Michael P. wrote: > > Look at the directory now. From the root directory there is a list of > > project names. There is absolutely no organization, other than an > > alphabetical listing by project name. > > This has not gone without notice, but we figured until we had some best > practices it's not worth diddling the repository in a half-ass manner. > It grew faster than expected.
I figured as much. If we recall the beginning of this email thread was - "what is the future direction". > > > A repository structured around > > FQDNs will provide an organized hierarchy of resources, help avoid > > project collision, and help identify resource providers. It will simply > > be more manageable. It is more than a formatted string. Repository > > organization guidelines provide much more than guaranteed uniqueness. > > Keep all your files on your computer in one directory for 1 year, and > > tell me how easy it is to find things or try programming with no package > > names. By enforcing some basic guidelines, repositories become easier > > for human/program to navigate. > > Certainly, which is why everything isn't in a _single_ directory. > Greater granularity is desired but when we make the switch it will be > the last time. Great! I don't have the answer myself, just suggesting possibilities. > > > What I'm suggesting is *much* more than resource organization, and > > multiple repositories. Using a de-centralized model for repositories, > > allows maven projects to resolve dependencies without needing to know > > the exact address of a server. > > I'm all for it. There needs to be a single cohesive repository for > archival and historical purposes but if you find a way to make > distributed behaviour work in a safe and synchronized manner then that's > great. But this is not as easy as it sounds. Understood, and I appreciate the support. - Mike > > > In a de-centralized model, as a developer, I can maintain my own > > repository (or repository cluster for my organization), manage my own > > distributions, and provide them immediately across *ALL* maven projects > > without each project needing to update any properties! > > Sounds like the PORTS type system Kurt was talking about a while ago. > Kurt, ring any bells? > > > - Mike > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > Sent: Monday, March 03, 2003 5:57 PM > > > To: Turbine Maven Developers List > > > Subject: Re: Update > > > > > > Mike (and Henning), > > > > > > if a string is not 'scalable', how is another formatted string more > > > scalable? > > > > > > I'm obviously missing something. Multiple repositories exist now, so > > > there's not a "everything in one repository on the planet" problem. > > > > > > What is it I'm missing? > > > -- > > > dIon Gillard, Multitask Consulting > > > Blog: http://www.freeroller.net/page/dion/Weblog > > > Work: http://www.multitask.com.au > > > > > > > > > "Henning P. Schmiedehausen" <[EMAIL PROTECTED]> wrote on 04/03/2003 > > > 09:44:42 AM: > > > > > > > "Stanley,Michael P." <[EMAIL PROTECTED]> writes: > > > > > > > > >> groupId is whatever someone chooses it to be. in the case of > > > > >> commons-collections, the groupId is commons-collections. > > > > > > > > >But that's kind of my point, this isn't scalable. A Project ID is > > not > > > > >necessarily unique. The large the repository grows the more > > > > >unmanageable it will become. > > > > > > > > Jason didn't understand this in the pre4 time frame. What makes you > > > > think that suddently he changed his mind? > > > > > > > > The whole "everything in one repository on the planet" approach is > > > > flawed. That's what I'm saying for four month now. And Jason gave me > > a > > > > "whiner" label because of that. > > > > > > > > Regards > > > > Henning > > > > > > > > -- > > > > Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH > > > > [EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/ > > > > > > > > Java, perl, Solaris, Linux, xSP Consulting, Web Services > > > > freelance consultant -- Jakarta Turbine Development -- hero for > > hire > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > > > For additional commands, e-mail: > > > [EMAIL PROTECTED] > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: turbine-maven-dev- > [EMAIL PROTECTED] > -- > jvz. > > Jason van Zyl > [EMAIL PROTECTED] > http://tambora.zenplex.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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
