[ 
https://issues.apache.org/jira/browse/LOG4J2-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Sicker closed LOG4J2-353.
------------------------------


> Use consistent conventions in configuration files
> -------------------------------------------------
>
>                 Key: LOG4J2-353
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-353
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Configurators
>    Affects Versions: 2.0-beta8
>         Environment: Apache Maven 3.0.5 
> (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 08:51:28-0500)
> Maven home: C:\Java\apache-maven-3.0.5\bin\..
> Java version: 1.7.0_25, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_25\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>            Reporter: Gary Gregory
>            Assignee: Gary Gregory
>
> Use consistent conventions in configuration files:
> - Elements are CamelCase
> - Attributes are camelCase
> This is just like ClassNames and instanceVariables in Java and other 
> languages.
> Names with hyphens like "some-ref", become SomeRef for an element and someRef 
> for an attribute.
> The current code is case-insensitive WRT configuration files and this issue 
> does not address case-sensitivity. If you use XML validation, the 
> configuration XSD expected the conventions listed above.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to