xpressly stated in the Sun
| coding standard.
|
|
| Restyling source is rude :)
|
| Hen
|
| On Wed, 2 Apr 2003, SPRINGER,IAN (HP-NewJersey,ex1) wrote:
|
| > I agree there are two camps. A decent way to compromise is
| to use explicit
| > imports unless there are n or more imports from a
I agree there are two camps. A decent way to compromise is to use explicit
imports unless there are n or more imports from a particular package.
I think more important than which style is used, is that the same style is
used consistently across a project. Doesn't Apache have any standard defined
| >* escapeJava now uses lowercase letters for hex codes. Are there any
| > feelings about switching to capital letters? I prefer caps (like
| > \uCAFE instead of \ucafe) but I could go either way.
I would vote for using uppercase, because this is what Sun uses
throughout the JDK.
--Ian
| On Thu, 27 Mar 2003, SPRINGER,IAN (HP-NewJersey,ex1) wrote:
|
| > Date: Thu, 27 Mar 2003 09:58:48 -0800
| > From: "SPRINGER,IAN (HP-NewJersey,ex1)" <[EMAIL PROTECTED]>
| > Reply-To: Jakarta Commons Developers List
| <[EMAIL PROTECTED]>
| > To: 'Jaka
| > I don't think you want to make commons-logging.properties contain
| > impl-specific config properties. Some impls might not even
| use a properties
| > file for their configuration - they might use XML or some
| other format.
| Well it might be nice to be able to specify the location of a con
| Hi,
|
| As I understand it, if I have a commons-logging.properties on my
| classpath then the concrete logger will use this properties file
| as its own configuration?
I don't think this is true.
| As it happens, I need to specify the log4.configuration system
| property to make it pick up i
