On Mon, 21 Oct 2002 18:53, Nicola Ken Barozzi wrote: > I agree that what you say is the most sensible and correct way...
but ... > The reality is that this *will* create tensions and flamewars. > 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. Never! Of course not. This has never happened before ! :) > IMHO using > > org.apache.common.* > > is a possible solution. icky IMHO. I still prefer just going with apache.commons.* It makes more semantic sense to me and still avoids all namespace conflicts. -- Cheers, Peter Donald He strains to hear a whisper who refuses to hear a shout.
