You might be irritated, but I think this is the cost to pay for working
around this obvious java lack of managing versioned libraries. I think it's just a matter of getting used to this package naming convention.
But it doesn't solve the problem.
The incompatabilities that usually hurt the most are the unplanned ones, like with collections. Your proposal is to change package with each incompatible new release. Well, applying that 'rule' to collections, I would not have changed package from 2 to 3 because as far as I was concerned at that time it WAS fully compatible. Only later did we find one constant that wasn't.
Stephen
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
