commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benedikt Ritter <>
Subject Re: [jira] [Resolved] (SANDBOX-389) [BeanUtils2] Implement populate() on DefaultBeanAccessor
Date Mon, 13 Feb 2012 22:50:11 GMT
Hi Simo,

thanks for applying my patches!

Sorry about the license header position. You told me that twice. Stupid 
eclipse does not understand that it has to put the imports under the 
license. I'll pay more attention to that.

And sorry about the tabs in pom.xml. I've configured eclipse to use 
spaces only. Sadly that does just affect the Java editor. Do you know a 
way to configure the pom source editor to use spaces instead of tabs?

About commons-lang version: your right, having a version property does 
only make sense when you're using several components of one vendor (like 
spring framework)

Have a nice start into the new week!

Am 13.02.2012 23:35, schrieb Simone Tripodi (Resolved) (JIRA):
>       [
> Simone Tripodi resolved SANDBOX-389.
> ------------------------------------
>      Resolution: Fixed
>        Assignee: Simone Tripodi
> Patch applied, see [r1243720|] but
>   * pay attention on new files where license header is located, its proper location is
{{before}} the import statements
>   * inverted logic in {{continue}} statements;
>   * *NO TABS* in pom XML;
>   * why did you think putting the {{commons-lang}} version as property would be a benefit?
>> [BeanUtils2] Implement populate() on DefaultBeanAccessor
>> ---------------------------------------------------------
>>                  Key: SANDBOX-389
>>                  URL:
>>              Project: Commons Sandbox
>>           Issue Type: Improvement
>>           Components: BeanUtils2
>>     Affects Versions: Nightly Builds
>>             Reporter: Benedikt Ritter
>>             Assignee: Simone Tripodi
>>          Attachments: SANDBOX-389.txt, SANDBOX-389v2.txt
>> Implement {{populate()}} as discussed on the ML (see
> --
> 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:

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

View raw message