On Sat, 14 Jun 2003, robert burrell donkin wrote:
maybe it's time to think about adding an optional package
(org.apache.commons.beantuils.optional?) and a build for a
beanutils-optional.jar inspired by the way that ant manages non-core
dependencies. this would allow new implementations with dependencies to be
added to the component without adding to the core-dependencies of
beanutils.
I would be +1 on doing this (at least until we were ready for a BeanUtils 2.x version where I'd be OK with adding dependencies) in ordser to accomodate an extended version of BasicDynaBean. I continue to be -1 on adding an external dependency in BeanUtils 1.x, for pretty much ANY reason (two years of use by lots of different folks makes it pretty clear that the "as is" package is pretty darn useful :-)
Quite frankly, the value add -- to BeanUtils users, not from the Lang perspective -- just isn't all that high. It exists, but not enough to disrupt the lives of the very large number of projects that currently depend on BeanUtils (see the Gump dependency chart for a small subset of the people that would be impacted by such a change).
i think that an optional jar will open up a lot of interesting avenues - not just for this, but for implementations of the bean query language strategies suggested by rune. even for 2.0, i think that we'd be serving everyone better if we kept the core dependencies to a minimum but factor beanutils in a more flexible way so that people could - if they wished - plug in more sophisticated strategies with more dependencies from the optional jar.
it's just a pity that i've got so little time at the moment and don't have the energy to push this forward...
- robert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
