Hi, I see the BeanUtils 1.7-dev already depends on commons collections 3.0-dev and builds OK. Can we update the dependency to collections 3.0 (final)?
i think that officially we're still on 2.0(?) but you're welcome to update the version number in the (unofficial) maven build.
maybe now we're on a mavenized documentation build, it'd be a good idea to try to get the official dependencies into the project.xml.
What's left to be done for the BeanUtils 1.7 release? I'd like to help...
as far i'm concerned, quite a lot. the interfaces for new classes need to be analysed before they are frozen by the release. it'd be better to come up with some minimal abstract classes which the present instances extend. we also need to think about which strategy plug-ins need to be factored out before we release.
there are also a *lot* of bug reports but many of them require thought before they can be resolved. i do have more energy now but beanutils isn't a major priority for me at the moment.
even when all that work's finished, we'd need a volunteer to act as release manager.
- robert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
