> From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED] > Sent: 21 October 2002 10:54
[...] > I agree that what you say is the most sensible and correct way... > > The reality is that this *will* create tensions and flamewars. Like we're seeing on [EMAIL PROTECTED] > Defining a different namespace will just make things easier, by avoiding > stupid discussions like the one that is happening now, because there > *are* people that just want to break balls as we say. *nod* > IMHO using > > org.apache.common.* > > is a possible solution. > > Also, when I say common_s_ I kept making errors in declarations because > I expected "common" since it's a "common" namespace, not a "commons" > namespace. Well, I find 'common' not too far off to object to it. We just have to make sure that it is well explained* what the Common PMC is about, since I can already see the confusion in such a name... It does feel like jumping through hoops though to fix earlier mistakes. Therefor I still think Jakarta Commons should fix their naming scheme. But that will have to be brought up there, not here. Sander *) and published prominently in an accesible webpage.
