changes to commons-beanutils distribution strategy

[robert burrell donkin <rd...@apache.org>]

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

Re: changes to commons-beanutils distribution strategy

[Stefan Bodewig <bo...@apache.org>]

On Sun, 23 May 2004, robert burrell donkin <rd...@apache.org> wrote:

> i think it best to split the beanutils project into two (one for
> core, the other for bean-collections).

Sounds reasonable.

> 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.

We should try this and adapt the descriptors if we find projects that
really need bean-collections.  In this case it's not unlikely that
we'll need to notify the projects since they may be expecting a single
jar that contains the whole of collections (a lot of builds copy jars
around).

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org