From: "Aaron Bannert" <[EMAIL PROTECTED]> > On Sat, Oct 19, 2002 at 08:50:37AM +1000, Peter Donald wrote: > > On Sat, 19 Oct 2002 04:07, Rodent of Unusual Size wrote: > > The one problem (at least in java land) is that classes are usually namespaced > > in reverse DNS order. ie > > > > org.apache.commons.X > > > > which will clash with jakarta commons. Apache.com does not seem to do java > > development work so it may be the case where we can move to > > > > apache.commons.X > > > > for the Apache commons - thus sidestepping namespace issues. Not sure though. > > That's a good point, but I suspect that the new Commons won't be stealing > the bottom-level names from Jakarta. For example, if... > > "org.apache.commons.Jfooness" is a Jakarta Commons project, then Commons > will just have to be careful not to reuse that prefix.
The problem here is that jakarta-commons project names are intended to be 'bland' (See the commons charter). Thus we have names such as lang, collections, io. These are names that might equally apply to other programming languages. My opinion is that putting code from different languages into the same CVS is just going to hurt. Stephen
