James Carman wrote:
I don't like forking all of commons together. To say
commons5-collections-1.0 doesn't work for me. Then, we have to get
all of
the commons projects to decide on "fork points." Am I understanding (c)
correctly?
I don't think there has to be commons-wide fork at all. I just see the
name change at the commons level rather than the package level being an
approach that can be useful to other packages, so that the other
projects that will inevitably make the switch can do so in a uniform
manner.
In the end, I'm most interested that whatever method is adopted be a
solution that can work for all of the commons projects that may want to
generify. BeanUtils could certainly be improved with generics, as could
Lang and others. In my shop, at least, we've been using JDK5 for over a
year now and the lack of progress towards creating generic versions of
the Commons components bespeaks a bit of stagnation. I've got the itch
for generics across the board; I'd like to be able to scratch it.
Kris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
