[EMAIL PROTECTED] writes:
>I tend to use uppercase in my code as well.. MyCustomXMLParser versus
>MyCustomXmlParser.. However, if you parse text documents,
>would it be MyCustomTextParser/MyCustomTXTParser? Something we may want to
>do as well is move them into their own utils/config directory?
MHO:
"Text" is a word, so it is "Text"
"TXT" is an abbreviation (no, it's an abomination, but that's another
story. ;-) ), so it is "TXT".
"XML" is an acronym, so "XML"
>I am going to work on getting the 1.0 proposal for Commons-config started
>this week, and I'll try and get a snapshot up on ibiblio.
Before you start this, I'd like to get the ClassPropertiesConfiguration
integrated in the factory, getting this, might make it possible to
really add .properties files to a jar (which was suggested by Daniel
if I remember correctly). This might be the matter of just setting up
another digester and doing some tests.
Also, it would be great if we would get something that can read Avalon
configuration files into commons-config before an 1.0 release.
And, as far as I can see, there is some work on the javadocs to be done
and maybe some code cleanup.
Regards
Henning
>Eric
>-----Original Message-----
>From: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED]
>Sent: Monday, June 09, 2003 8:07 AM
>To: [EMAIL PROTECTED]
>Subject: Re: cvs commit:
>jakarta-turbine-2/src/java/org/apache/turbine/util TurbineConfig.java
>"Quinton McCombs" <[EMAIL PROTECTED]> writes:
>>In the future, if you need to rollback after a commit, just check out the
>>previous version and then copy/paste over the current version and check it
>>back in.
>You can't do that, because if you check out a previous version with -r, you
>will get a "sticky" file. You can do a checkout with
>cvs checkout -r<old_version> -p <botched_file> > <botched_file>
>to avoid this.
>[...]
>>I actually have the same habit of always format the code and optimize
>>imports. What keeps me from making the same mistakes is that I _always_ do
>>a cvs diff before I commit anything. An added benefit to this step is that
>>you have one final chance to make sure that your commit message covers all
>>of the changes. This is a very good habit to have.
>Same here. :-)
>Eric, BTW: Shouldn't this be called TurbineXMLConfig instead of
>TurbineXmlConfig ? I remember the discussion about acronyms and even
>Sun did deprecate some of the Ucase in favour of UCASE.
> Regards
> Henning
>--
>Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
>[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
>Java, perl, Solaris, Linux, xSP Consulting, Web Services
>freelance consultant -- Jakarta Turbine Development -- hero for hire
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>------_=_NextPart_001_01C32E80.91B47440--
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
