commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simone Tripodi (Commented) (JIRA)" <>
Subject [jira] [Commented] (SANDBOX-379) [BeanUtils2] Implement describe() on DefaultBeanAccessor
Date Thu, 02 Feb 2012 10:49:55 GMT


Simone Tripodi commented on SANDBOX-379:


So I thought creating a new test for DefaultBeanAccessor would be a good idea, regarding separation
of concerns. What do you think?

so split per-functionalities, {{DefaultBeanAccessor}} would contain the biggest amount of

I really liked the idea to have a dedicated test for a bug. To be honest, I was thinking about
proposing that in my company  But if you don't like it, I'll move it depending on your comment
to the above mentioned topic.

it's not a matter of taste, sometimes (depending on the bug) I do the same in projects that
have already been released, not in an experiment. The bug is known and fixed in a previous
version of the component, references in comments are fine but don't see the advantage of dedicated
test in a new version.

alles gute!
> [BeanUtils2] Implement describe() on DefaultBeanAccessor 
> ---------------------------------------------------------
>                 Key: SANDBOX-379
>                 URL:
>             Project: Commons Sandbox
>          Issue Type: Improvement
>          Components: BeanUtils2
>    Affects Versions: Nightly Builds
>            Reporter: Benedikt Ritter
>         Attachments: SANDBOX-379.txt
> Implement the above mentioned method an corresponding unit tests

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message