commons-beanutils has recently been reorganized into core (with no dependency on commons-collections) and a second jar that contains bean related implementations directly dependent on commons-collections. some recent beanutils failures appear to be caused by these changes.

i think it best to split the beanutils project into two (one for core, the other for bean-collections). i don't think that any other projects depend on the code in bean-collections so the dependencies can be updated to just the core. i've attached a patch with these changes in.

- robert


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to