we've talked before about removing the dependency of beanutils on collections. there are two parts to this, the first is to come up with a solution to the issue of fasthashmap, the second is what to do about BeanPropertyValueChangeClosure, BeanPropertyValueEqualsPredicate and BeanToPropertyValueTransformer.

i'd like to propose that we solve the second problem by a home for optional classes with non-core dependencies and move these classes into it.

i'd prefer to use a maven-friendly subdirectory called 'optional' with commons/beanutils with a complete maven-friendly directory structure. for distribution, we create a beanutils-optional.jar but include that within the main distribution (in a similar way to ant).

comments please :)

- robert


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



Reply via email to