Peter Donald wrote:
On Sat, 19 Oct 2002 08:51, Nicola Ken Barozzi wrote:
Actually I don't see the problem, since Jakarta Commons is about common Java code, and commons is about common java code...
Some projects will migrate before, some later, some never, but I'm sure overlap will not be necessary, as the proposed *bleah* solution ;-P
It has nothing to do with migration or non-migration. The problem will be name clashes. What happens when we migrate large chunks of the Excalibur codebase(s) over. Who gets the "CLI" name or whatever? Even if we mangle names we will still have a problem in the future - ie what happens when jakarta-commons accepts a "beanbag" component and Apache Commons already has one?
Yeah, you're right, I'm too optimistic :-/
We don't want to have to deal with coliisions in released and we don't want to have to worry about "claim" jumping.
I never remember that avoiding potential problems with egos floating around is good... your involvement in previous collision discussions that is now talking advises us well... you are right.
Hence it would be better IMHO to have separate namespaces.
what about
org.apache.commons.*
org.apache.common.*
?
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------