Guten morgen, Jörg!

> JDK has actually XMLWriter as well as XmlWriter :D
>

lol indeed, that's fun! :D

> However, since is more of a personal preference, I'd not set up any rule for
> all Apache commons components, we should just try to keep it consistent
> within a component.
>

+1, no doubts!

> While I know that Gary would like to finalize the API for 1.0 I'd personally
> find it annoying if I had to change code just because of a personal
> preference (using SNAPSHOTs of CVS for long times - and I bet I am not the
> only one using SNAPSHOTs after so much years this component is floating
> around). As long as it's consistent I'd simply keep it now.

agreed, at Apache Any23 we are using CVS SNAPSHOTs as well, that would
imply a refactory...

all the best!
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/


On Wed, Sep 12, 2012 at 11:24 AM, Jörg Schaible
<joerg.schai...@scalaris.com> wrote:
> Hi Simo,
>
> Simone Tripodi wrote:
>
>>>> Any agreement (or objection) on changing that?
>>>
>>> Why? CSV is an acronym and as such capital letters are OK.
>>
>> I remember a thread where we discussed about that, unfortunately I
>> cannot find it anymore (quickly tried a little on markmail but with no
>> success) - not sure we arrived somewhere - but I remember there where
>> two "schools of thought" about it: I personally prefer the Gary's one,
>> i.e. XmlParser rather than XMLParser.
>
> JDK has actually XMLWriter as well as XmlWriter :D
>
> However, since is more of a personal preference, I'd not set up any rule for
> all Apache commons components, we should just try to keep it consistent
> within a component.
>
> While I know that Gary would like to finalize the API for 1.0 I'd personally
> find it annoying if I had to change code just because of a personal
> preference (using SNAPSHOTs of CVS for long times - and I bet I am not the
> only one using SNAPSHOTs after so much years this component is floating
> around). As long as it's consistent I'd simply keep it now.
>
> - Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to