Remko Popma created LOG4J2-1156:
-----------------------------------

             Summary: 2.4.1 web site corrections and updates
                 Key: LOG4J2-1156
                 URL: https://issues.apache.org/jira/browse/LOG4J2-1156
             Project: Log4j 2
          Issue Type: Improvement
          Components: Documentation
    Affects Versions: 2.4.1
            Reporter: Remko Popma


*faq.html*
\- Starting with version 2.4, Log4j 2 provides an \[API for programmatic 
configuration|manual/customconfig.html]. 
+  Starting with version 2.4, Log4j 2 provides an <a 
href="manual/customconfig.html">API for programmatic configuration</a>.

\- You need at least the log4j-api-2.4 and the log4j-core-2.4 jar files.
+ You need at least the log4j-api-2.x and the log4j-core-2.x jar files.

* Update image file under "Which jars" to specify "2.x" instead of "2.1"

*manual/configuration.html*
\- Through a configuration file written in XML, JSON, or YAML.
+ Through a configuration file written in XML, JSON, YAML, or properties format.

\- Information on programmatically configuring Log4j can be found at <a 
href="extending.html">Extending Log4j 2</a>.
+ Information on programmatically configuring Log4j can be found at <a 
href="extending.html">Extending Log4j 2</a> and <a 
href="customconfig.html">Programmatic Log4j Configuration</a>.

* Under "Automatic Configuration" there is no mention of the properties format, 
the expected configuration file name for properties files or in what order 
Log4j 2 tries to discover log4j2.properties file relative to the order formats.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to