I wasn't part of the decision at the time, but (at least some if not all) these classes are in the BeanUtils public API so changing the package would have (and still will) broken binary compatibility (to remove the dependency on Collections 'coz of its incompatibility between versions!) - they were copied and (AFAIK) the parts of the public API deprecated with the intention of removing them in the next release - but there hasn't been one since that was done and 1.7.0 released.
Niall On 5/18/07, Torsten Curdt <[EMAIL PROTECTED]> wrote:
Yepp! We should change the package name and push out a new release. cheers -- Torsten On 18.05.2007, at 13:10, James Carman wrote: > The real question is why didn't we change the package names so as > to not > collide with the real classes if you have them in your classpath > also. I > realize that it was required by the public API, but I think having > people > change an import statement here and there would be accepted more > readily > than having them chase down a classloading issue where they're > using the > Buffer impl in the beanutils jar rather than collections jar. > > On 5/18/07, Niall Pemberton <[EMAIL PROTECTED]> wrote: >> >> On 5/18/07, Torsten Curdt <[EMAIL PROTECTED]> wrote: >> > Grrrr... why oh why are commmons collection classes inside >> beanutils?! >> >> http://tinyurl.com/yvma2q >> http://tinyurl.com/2hs3hp >> >> Niall >> >> > @[EMAIL PROTECTED]@ >> > -- >> > Torsten
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
