Sander Striker wrote:
From: Nicola Ken Barozzi [mailto:nicolaken@;apache.org] 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 reorg@.
Then you've seen nothing yet ;-)
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.
Feels? ;-) It *is* hehehe
It's completely impractical, and will hurt Jakarta immensely.Therefor I still think Jakarta Commons should fix their naming scheme. But that will have to be brought up there, not here.
Oh, well, now that I think of it, this is only for projects that have already been released...
Other opinions?
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:general-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:general-help@;jakarta.apache.org>
