now that the beanutils release is reaching toward completion, i'm turning towards the digester release. the release branch was created a while ago but there are still some thing which need to be decided.

one important issue are the dependencies: in particular, disposing with the commons collection dependency (which prevents compatibility with both 2.x and 3.x).

i can see two possibilities: either we upgrade the beanutils dependency to the latest release (which contains the collections classes that digester depends on) or we keep the current beanutils dependency and add the necessary classes (as a temporary measure until the appropriate methods are deprecated).

originally, i'd assumed that we'd automatically just upgrade the beanutils dependency but (previously) stephen made some good arguments for added the classes where necessary. anyone else have any opinions?

- robert


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



Reply via email to