There is one more collection that should be added to beanutils-collections.jar. That is BeanMap, currently situated in [collections]. This should be copied and repackaged, enabling collections to deprecate its version. (If beanutils is quick about its release then I could deprecate in collections 3.1)
I want to eject it from [collections], as it fits logically better with [beanutils] (as it deals with beans and reflection) and is quite a large size. The test cases can now be taken too, as [collections] produces its test framework as a jar. Stephen From: "robert burrell donkin" <[EMAIL PROTECTED]> > >> 3 factor out a new bean-collections jar under extras/bean-collections > >> containing the (cool) implementations of collections stuffs using > >> beanutils bean-magic. > >> > > I'm not sure I'm parsing this sentence correctly. Does that mean we > > just put the ArrayStack and Buffer and Fast* classes being grabbed > > here, instead of in src/java? If so, +1. Otherwise, could you please > > explain further? > > there are five classes that have direct dependencies on the core of > collections: > BeanComparator > BeanPredicate > BeanPropertyValueChangeClosure > BeanPropertyValueEqualsPredicate > BeanToPropertyValueTransformer > > i'm pretty sure that these have been added since the last release (but > i will check that). these all operate on collections of beans using the > core collections abstracts and so have real dependencies on collections > (3.0). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
