commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Colebourne (JIRA)" <>
Subject [jira] Commented: (BEANUTILS-285) Consider options for BeanUtils compatibility in light of Conversion improvements
Date Sat, 30 Jun 2007 09:37:04 GMT


Stephen Colebourne commented on BEANUTILS-285:

Although I haven't followed the detail of this case, ensuring it is fully semantically, binary
and source compatible is essential IMO. These are exceptionally widely distributed libraries,
and having anything change in them that breaks others will create all sorts of dependency

Maybe the better solution here is to get commons-convert working and released, as a simple
object-string conversion tool (the original plan), and then allow [beanutils] to optionally
use [convert] as the conversion provider instead of the old (rolled back) converters in [beanutils]

> Consider options for BeanUtils compatibility in light of Conversion improvements
> --------------------------------------------------------------------------------
>                 Key: BEANUTILS-285
>                 URL:
>             Project: Commons BeanUtils
>          Issue Type: New Feature
>          Components: ConvertUtils & Converters
>    Affects Versions: 1.8.0
>            Reporter: Niall Pemberton
>            Assignee: Niall Pemberton
>         Attachments: betwixt-beanutils-gump-fix.patch
> The Conversion improvements associated with BEANUTILS-258 potentially create compatibility
issues - this was highlighted by Betwixt's tests failing recently in the gump run - see
for more details.
> Quite a bit of effort has been put into making the new conversion facilities as painless
as possible for existing users. However it is not fully backwards compatible in terms of behaviour
(stiil binary compatible). Need to give this some consideration before a BeanUtils release
- at the moment there are two options on the table (more welcome!):
> 1) The compatibility as it stands is good enough (covers most cases) - so do nothing
> 2) Provide a "compatibility option" - so that users can choose either the new behaviour
or behaviour compatible with BeanUtils 1.7.0. This probably involves quite a bit of work -
adding back the old behaviour alongside the new

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message