You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Ralph Goers <ra...@dslextreme.com> on 2019/06/26 03:59:29 UTC

[VOTE] Release Log4j 2.12.0-rc2

This is a vote to release Log4j 2.12.0, the next version of the Log4j 2 project.

Please download, test, and cast your votes on the log4j developers list.
[] +1, release the artifacts
[] -1, don't release because...

The vote will remain open for 72 hours (or more if required). All votes are welcome and we encourage everyone to test the release, but only Logging PMC votes are “officially” counted. As always, at least 3 +1 votes and more positive than negative votes are required.

Changes in this release include:

New Features

	• LOG4J2-2403: Allow zero padding the counter of a RollingFileAppender. Thanks to hupfdule.
	• LOG4J2-2427: Add filter that will match events when no marker is present. Thanks to Rimaljit Kaur.
	• LOG4J2-2406: Add reconfiguration methods to Configurator.
	• LOG4J2-913: Add support for reconfiguration via HTTP(S), Docker, and Spring Cloud Configuration.
	• LOG4J2-2586: TCP Appender should support a host name resolving to multiple IP addresses.
	• LOG4J2-2337: Allow custom end-of-line with JsonLayout. Thanks to Arvind Sahare, Patrice Ferrot.
	• LOG4J2-2598: GZIP compression on rollover supports configurable compression levels. Thanks to Carter Kozak.
	• LOG4J2-2611: AsyncQueueFullPolicy configuration short values "Default" and "Discard" are case insensitive to avoid confusion.
	• LOG4J2-2634: Add and use method org.apache.logging.log4j.message.MapMessage.toKey(String) for simpler subclasses.
Fixed Bugs

	• LOG4J2-2547: RollingRandomAccessFileAppender error message referenced incorrect class name.
	• LOG4J2-2616: Restore constructor to ThrowablePatternConverter that was removed in 2.8.2.
	• LOG4J2-2622: StructuredDataId was ignoring maxLength atribute.
	• LOG4J2-2636: RFC5424Layout was not properly setting default Structured Element id for the MDC
	• LOG4J2-1143: Lookups were not found if the plugin key was not lowercase. Thanks to Pascal Heinrich.
	• LOG4J2-1852: Locate plugins within a Jar using a URL Connection. Thanks to Tanner Altares.
	• LOG4J2-2610: Explicitly set file creation time.
	• LOG4J2-2561: JEP223 version detection fix for JDK 9 and up. Thanks to Ulrich Enslin.
	• LOG4J2-1103: FailoverAppender was failing with ERROR appender Failover has no parameter that matches element Failovers. Thanks to Seán Dunne.
	• LOG4J2-2602: Update file time when size based triggering policy is used without a time-based triggering policy.
	• LOG4J2-2597: Throw better exception message when both log4j-slf4j-impl and log4j-to-slf4j are present.
	• LOG4J2-2559: NullPointerException in JdbcAppender.createAppender(). Thanks to Li Lei, Gary Gregory.
	• LOG4J2-2592: StackOverflowException when server not reachable with SocketAppender. Thanks to Dávid Kaya, Gary Gregory.
	• LOG4J2-2598: java.lang.StackOverflowError at org.apache.logging.log4j.junit.AbstractExternalFileCleaner.println(AbstractExternalFileCleaner.java:169). Thanks to Gary Gregory.
	• LOG4J2-2564: MapPatternConverter is properly created from the '%K', '%map', and '%MAP' patterns. PatternConverter instanceOf methods with unknown parameter types no longer elide those with known parameters.
	• LOG4J2-2612: NullPointerException at org.apache.logging.log4j.core.appender.db.jdbc.JdbcDatabaseManager.writeInternal(JdbcDatabaseManager.java:803).
	• LOG4J2-2618: Possible ClassCastException in org.apache.logging.log4j.core.script.ScriptManager.ScriptManager(Configuration, WatchManager)
	• LOG4J2-2631: RoutingAppender PurgePolicy implementations no longer stop appenders referenced from the logger configuration, only those that have been created by the RoutingAppender. Note that RoutingAppender.getAppenders no longer includes entries for referenced appenders, only those which it has created.
	• LOG4J2-2629: Fix a race allowing events not to be recorded when a RoutingAppender purge policy attempts to delete an idle appender at exactly the same time as a new event is recorded.
	• LOG4J2-2606: Asynchronous logging when the queue is full no longer results in heavy CPU utilization and low throughput.
Changes

	• : Update tests from H2 1.4.197 to 1.4.199. Thanks to Gary Gregory.
	• LOG4J2-2570: Update Jackson from 2.9.7 to 2.9.8. Thanks to Gary Gregory.
	• LOG4J2-2574: Update MongoDB 3 module driver from 3.9.0 to 3.10.1. Thanks to Gary Gregory.
	• LOG4J2-2619: Update Jackson from 2.9.8 to 2.9.9.
	• LOG4J2-2634: Refactor several AsyncLogger methods below the 35 byte threshold for inlining.

Tag: 
a)  for a new copy do "git clone https://github.com/apache/logging-log4j2.git" and then "git checkout tags/log4j-2.12.0-rc2” 
b) for an existing working copy to “git pull” and then “git checkout tags/log4j-2.12.0-rc2”

Web Site:  http://rgoers.github.io/log4j2-site/index.html.

Maven Artifacts: https://repository.apache.org/content/repositories/orgapachelogging-1047

Distribution archives: https://dist.apache.org/repos/dist/dev/logging/log4j/ 

You may download all the Maven artifacts by executing:
wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate https://repository.apache.org/content/repositories/orgapachelogging-1047/org/apache/logging/log4j/

Ralph

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Remko Popma <re...@gmail.com>.
+1

The mongodb tests hung for me, but if I skip those, the tests pass.


On Wed, Jun 26, 2019 at 10:08 PM Ralph Goers <ra...@dslextreme.com>
wrote:

> That is interesting. As part of the pre-release process I run mvn -P rat
> -DskipTests clean verify and that succeeded.
>
> Ralph
>
> > On Jun 26, 2019, at 5:58 AM, Gary Gregory <ga...@gmail.com>
> wrote:
> >
> > On Wed, Jun 26, 2019 at 8:40 AM Gary Gregory <ga...@gmail.com>
> wrote:
> >
> >> FYI, running 'mvn apache-rat:check' fails on log4j-cassandra/.toDelete
> >>
> >
> > Ah, I can see that we have .gitignore set up to ignore this file so I
> > deleted it and ran 'mvn apache-rat:check' again and got:
> >
> > [INFO] --<
> > org.apache.logging.log4j.samples:log4j-spring-cloud-config-sample-server
> >--
> > [INFO] Building Log4j Sample Configuration Service 2.12.0
> > [38/40]
> > [INFO] --------------------------------[ jar
> > ]---------------------------------
> > [WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is
> > missing, no dependency information available
> > [WARNING] Failed to retrieve plugin descriptor for
> > org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin
> > org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could
> > not be resolved: Failure to find
> > org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 in
> > https://repo.maven.apache.org/maven2 was cached in the local repository,
> > resolution will not be reattempted until the update interval of central
> has
> > elapsed or updates are forced
> > Downloading from central:
> >
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> > Downloading from central:
> >
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
> > Downloaded from central:
> >
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> > (14 kB at 17 kB/s)
> > Downloaded from central:
> >
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
> > (20 kB at 26 kB/s)
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Reactor Summary for Apache Log4j 2 2.12.0:
> > [INFO]
> > [INFO] Apache Log4j 2 ..................................... SUCCESS [
> > 1.859 s]
> > [INFO] Apache Log4j API Java 9 support .................... SUCCESS [
> > 0.125 s]
> > [INFO] Apache Log4j API ................................... SUCCESS [
> > 0.454 s]
> > [INFO] Apache Log4j Implementation Java 9 support ......... SUCCESS [
> > 0.079 s]
> > [INFO] Apache Log4j Core .................................. SUCCESS [
> > 1.183 s]
> > [INFO] Apache Log4j Core Integration Tests ................ SUCCESS [
> > 0.088 s]
> > [INFO] Apache Log4j 1.x Compatibility API ................. SUCCESS [
> > 0.198 s]
> > [INFO] Apache Log4j to SLF4J Adapter ...................... SUCCESS [
> > 0.082 s]
> > [INFO] Apache Log4j SLF4J Binding ......................... SUCCESS [
> > 0.099 s]
> > [INFO] Apache Log4j SLF4J 1.8+ Binding .................... SUCCESS [
> > 0.095 s]
> > [INFO] Apache Log4j Commons Logging Bridge ................ SUCCESS [
> > 0.092 s]
> > [INFO] Apache Log4j Flume Bridge .......................... SUCCESS [
> > 0.090 s]
> > [INFO] Apache Log4j Web ................................... SUCCESS [
> > 0.092 s]
> > [INFO] Apache Log4j Tag Library ........................... SUCCESS [
> > 0.104 s]
> > [INFO] Apache Log4j JMX GUI ............................... SUCCESS [
> > 0.082 s]
> > [INFO] Apache Log4j Samples ............................... SUCCESS [
> > 0.113 s]
> > [INFO] Apache Log4j Samples: Flume - Common ............... SUCCESS [
> > 0.085 s]
> > [INFO] Apache Log4j Samples: Flume - Remote ............... SUCCESS [
> > 0.075 s]
> > [INFO] Apache Log4j Samples: Flume - Embedded ............. SUCCESS [
> > 0.079 s]
> > [INFO] Apache Log4j Samples: Configuration ................ SUCCESS [
> > 0.069 s]
> > [INFO] Apache Log4j Samples: LoggerProperties ............. SUCCESS [
> > 0.084 s]
> > [INFO] Apache Log4j BOM ................................... SUCCESS [
> > 0.189 s]
> > [INFO] Apache Log4j JDBC DBCP 2 ........................... SUCCESS [
> > 0.069 s]
> > [INFO] Apache Log4j JPA ................................... SUCCESS [
> > 0.112 s]
> > [INFO] Apache Log4j CouchDB ............................... SUCCESS [
> > 0.073 s]
> > [INFO] Apache Log4j MongoDB 2 ............................. SUCCESS [
> > 0.082 s]
> > [INFO] Apache Log4j MongoDB 3 ............................. SUCCESS [
> > 0.091 s]
> > [INFO] Apache Log4j Cassandra ............................. SUCCESS [
> > 0.076 s]
> > [INFO] Apache Log4J Performance Tests ..................... SUCCESS [
> > 0.273 s]
> > [INFO] Apache Log4j Streaming Interface ................... SUCCESS [
> > 0.103 s]
> > [INFO] Apache Log4j JUL Adapter ........................... SUCCESS [
> > 0.093 s]
> > [INFO] Apache Log4j Liquibase Binding ..................... SUCCESS [
> > 0.067 s]
> > [INFO] Apache Log4j App Server Support .................... SUCCESS [
> > 0.071 s]
> > [INFO] Apache Log4j OSGi .................................. SUCCESS [
> > 0.071 s]
> > [INFO] Apache Log4j Docker Library ........................ SUCCESS [
> > 0.081 s]
> > [INFO] Apache Log4j Spring Cloud Config Support ........... SUCCESS [
> > 0.110 s]
> > [INFO] Apache Log4j Spring Cloud Config Client Support .... SUCCESS [
> > 0.083 s]
> > [INFO] Log4j Sample Configuration Service ................. FAILURE [
> > 1.429 s]
> > [INFO] Apache Log4j Spring Cloud Config Samples ........... SKIPPED
> > [INFO] Spring Cloud Config Sample Application ............. SKIPPED
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] BUILD FAILURE
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Total time:  10.809 s
> > [INFO] Finished at: 2019-06-26T08:55:03-04:00
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] No plugin found for prefix 'apache-rat' in the current project
> and
> > in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo]
> > available from the repositories [local
> (C:\Users\ggregory\.m2\repository),
> > central (https://repo.maven.apache.org/maven2)] -> [Help 1]
> > [ERROR]
> > [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e
> > switch.
> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> > [ERROR]
> > [ERROR] For more information about the errors and possible solutions,
> > please read the following articles:
> > [ERROR] [Help 1]
> >
> http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundForPrefixException
> >
> > How does that make any sense?
> >
> > Gary
> >
> >
> >>
> >> Gary
> >>
> >> On Tue, Jun 25, 2019 at 11:59 PM Ralph Goers <
> ralph.goers@dslextreme.com>
> >> wrote:
> >>
> >>> This is a vote to release Log4j 2.12.0, the next version of the Log4j 2
> >>> project.
> >>>
> >>> Please download, test, and cast your votes on the log4j developers
> list.
> >>> [] +1, release the artifacts
> >>> [] -1, don't release because...
> >>>
> >>> The vote will remain open for 72 hours (or more if required). All votes
> >>> are welcome and we encourage everyone to test the release, but only
> Logging
> >>> PMC votes are “officially” counted. As always, at least 3 +1 votes and
> more
> >>> positive than negative votes are required.
> >>>
> >>> Changes in this release include:
> >>>
> >>> New Features
> >>>
> >>>        • LOG4J2-2403: Allow zero padding the counter of a
> >>> RollingFileAppender. Thanks to hupfdule.
> >>>        • LOG4J2-2427: Add filter that will match events when no marker
> >>> is present. Thanks to Rimaljit Kaur.
> >>>        • LOG4J2-2406: Add reconfiguration methods to Configurator.
> >>>        • LOG4J2-913: Add support for reconfiguration via HTTP(S),
> >>> Docker, and Spring Cloud Configuration.
> >>>        • LOG4J2-2586: TCP Appender should support a host name resolving
> >>> to multiple IP addresses.
> >>>        • LOG4J2-2337: Allow custom end-of-line with JsonLayout. Thanks
> >>> to Arvind Sahare, Patrice Ferrot.
> >>>        • LOG4J2-2598: GZIP compression on rollover supports
> configurable
> >>> compression levels. Thanks to Carter Kozak.
> >>>        • LOG4J2-2611: AsyncQueueFullPolicy configuration short values
> >>> "Default" and "Discard" are case insensitive to avoid confusion.
> >>>        • LOG4J2-2634: Add and use method
> >>> org.apache.logging.log4j.message.MapMessage.toKey(String) for simpler
> >>> subclasses.
> >>> Fixed Bugs
> >>>
> >>>        • LOG4J2-2547: RollingRandomAccessFileAppender error message
> >>> referenced incorrect class name.
> >>>        • LOG4J2-2616: Restore constructor to ThrowablePatternConverter
> >>> that was removed in 2.8.2.
> >>>        • LOG4J2-2622: StructuredDataId was ignoring maxLength atribute.
> >>>        • LOG4J2-2636: RFC5424Layout was not properly setting default
> >>> Structured Element id for the MDC
> >>>        • LOG4J2-1143: Lookups were not found if the plugin key was not
> >>> lowercase. Thanks to Pascal Heinrich.
> >>>        • LOG4J2-1852: Locate plugins within a Jar using a URL
> >>> Connection. Thanks to Tanner Altares.
> >>>        • LOG4J2-2610: Explicitly set file creation time.
> >>>        • LOG4J2-2561: JEP223 version detection fix for JDK 9 and up.
> >>> Thanks to Ulrich Enslin.
> >>>        • LOG4J2-1103: FailoverAppender was failing with ERROR appender
> >>> Failover has no parameter that matches element Failovers. Thanks to
> Seán
> >>> Dunne.
> >>>        • LOG4J2-2602: Update file time when size based triggering
> policy
> >>> is used without a time-based triggering policy.
> >>>        • LOG4J2-2597: Throw better exception message when both
> >>> log4j-slf4j-impl and log4j-to-slf4j are present.
> >>>        • LOG4J2-2559: NullPointerException in
> >>> JdbcAppender.createAppender(). Thanks to Li Lei, Gary Gregory.
> >>>        • LOG4J2-2592: StackOverflowException when server not reachable
> >>> with SocketAppender. Thanks to Dávid Kaya, Gary Gregory.
> >>>        • LOG4J2-2598: java.lang.StackOverflowError at
> >>>
> org.apache.logging.log4j.junit.AbstractExternalFileCleaner.println(AbstractExternalFileCleaner.java:169).
> >>> Thanks to Gary Gregory.
> >>>        • LOG4J2-2564: MapPatternConverter is properly created from the
> >>> '%K', '%map', and '%MAP' patterns. PatternConverter instanceOf methods
> with
> >>> unknown parameter types no longer elide those with known parameters.
> >>>        • LOG4J2-2612: NullPointerException at
> >>>
> org.apache.logging.log4j.core.appender.db.jdbc.JdbcDatabaseManager.writeInternal(JdbcDatabaseManager.java:803).
> >>>        • LOG4J2-2618: Possible ClassCastException in
> >>>
> org.apache.logging.log4j.core.script.ScriptManager.ScriptManager(Configuration,
> >>> WatchManager)
> >>>        • LOG4J2-2631: RoutingAppender PurgePolicy implementations no
> >>> longer stop appenders referenced from the logger configuration, only
> those
> >>> that have been created by the RoutingAppender. Note that
> >>> RoutingAppender.getAppenders no longer includes entries for referenced
> >>> appenders, only those which it has created.
> >>>        • LOG4J2-2629: Fix a race allowing events not to be recorded
> when
> >>> a RoutingAppender purge policy attempts to delete an idle appender at
> >>> exactly the same time as a new event is recorded.
> >>>        • LOG4J2-2606: Asynchronous logging when the queue is full no
> >>> longer results in heavy CPU utilization and low throughput.
> >>> Changes
> >>>
> >>>        • : Update tests from H2 1.4.197 to 1.4.199. Thanks to Gary
> >>> Gregory.
> >>>        • LOG4J2-2570: Update Jackson from 2.9.7 to 2.9.8. Thanks to
> Gary
> >>> Gregory.
> >>>        • LOG4J2-2574: Update MongoDB 3 module driver from 3.9.0 to
> >>> 3.10.1. Thanks to Gary Gregory.
> >>>        • LOG4J2-2619: Update Jackson from 2.9.8 to 2.9.9.
> >>>        • LOG4J2-2634: Refactor several AsyncLogger methods below the 35
> >>> byte threshold for inlining.
> >>>
> >>> Tag:
> >>> a)  for a new copy do "git clone
> >>> https://github.com/apache/logging-log4j2.git" and then "git checkout
> >>> tags/log4j-2.12.0-rc2”
> >>> b) for an existing working copy to “git pull” and then “git checkout
> >>> tags/log4j-2.12.0-rc2”
> >>>
> >>> Web Site:  http://rgoers.github.io/log4j2-site/index.html.
> >>>
> >>> Maven Artifacts:
> >>>
> https://repository.apache.org/content/repositories/orgapachelogging-1047
> >>>
> >>> Distribution archives:
> >>> https://dist.apache.org/repos/dist/dev/logging/log4j/
> >>>
> >>> You may download all the Maven artifacts by executing:
> >>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
> >>>
> https://repository.apache.org/content/repositories/orgapachelogging-1047/org/apache/logging/log4j/
> >>>
> >>> Ralph
> >>>
> >>
>
>

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Ralph Goers <ra...@dslextreme.com>.
It occurs to me that the module that is failing for you is a Spring Boot app so it inherits from Spring Boot parent. So when I run mvn -P rat clean verify it won’t run rat because that module doesn’t have a rat plugin defined. When you run apache-rat:check it will fail because you explicitly told it to run the plugin and there is no configuration for it.  I’ll configure something and see if there are any problems with the license header. If there aren’t we can just fix it for the next release.

Ralph

> On Jun 26, 2019, at 7:22 AM, Gary Gregory <ga...@gmail.com> wrote:
> 
> On Wed, Jun 26, 2019 at 9:08 AM Ralph Goers <ra...@dslextreme.com>
> wrote:
> 
>> That is interesting. As part of the pre-release process I run mvn -P rat
>> -DskipTests clean verify and that succeeded.
>> 
> 
> Your command works for me as well, no surprise and a good thing. But
> replacing '-P rat' with 'apache-rat:check' in that command fails. Weird.
> 
> I will keep on testing.
> 
> Gary
> 
> 
>> 
>> Ralph
>> 
>>> On Jun 26, 2019, at 5:58 AM, Gary Gregory <ga...@gmail.com>
>> wrote:
>>> 
>>> On Wed, Jun 26, 2019 at 8:40 AM Gary Gregory <ga...@gmail.com>
>> wrote:
>>> 
>>>> FYI, running 'mvn apache-rat:check' fails on log4j-cassandra/.toDelete
>>>> 
>>> 
>>> Ah, I can see that we have .gitignore set up to ignore this file so I
>>> deleted it and ran 'mvn apache-rat:check' again and got:
>>> 
>>> [INFO] --<
>>> org.apache.logging.log4j.samples:log4j-spring-cloud-config-sample-server
>>> --
>>> [INFO] Building Log4j Sample Configuration Service 2.12.0
>>> [38/40]
>>> [INFO] --------------------------------[ jar
>>> ]---------------------------------
>>> [WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is
>>> missing, no dependency information available
>>> [WARNING] Failed to retrieve plugin descriptor for
>>> org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin
>>> org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could
>>> not be resolved: Failure to find
>>> org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 in
>>> https://repo.maven.apache.org/maven2 was cached in the local repository,
>>> resolution will not be reattempted until the update interval of central
>> has
>>> elapsed or updates are forced
>>> Downloading from central:
>>> 
>> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
>>> Downloading from central:
>>> 
>> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
>>> Downloaded from central:
>>> 
>> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
>>> (14 kB at 17 kB/s)
>>> Downloaded from central:
>>> 
>> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
>>> (20 kB at 26 kB/s)
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Reactor Summary for Apache Log4j 2 2.12.0:
>>> [INFO]
>>> [INFO] Apache Log4j 2 ..................................... SUCCESS [
>>> 1.859 s]
>>> [INFO] Apache Log4j API Java 9 support .................... SUCCESS [
>>> 0.125 s]
>>> [INFO] Apache Log4j API ................................... SUCCESS [
>>> 0.454 s]
>>> [INFO] Apache Log4j Implementation Java 9 support ......... SUCCESS [
>>> 0.079 s]
>>> [INFO] Apache Log4j Core .................................. SUCCESS [
>>> 1.183 s]
>>> [INFO] Apache Log4j Core Integration Tests ................ SUCCESS [
>>> 0.088 s]
>>> [INFO] Apache Log4j 1.x Compatibility API ................. SUCCESS [
>>> 0.198 s]
>>> [INFO] Apache Log4j to SLF4J Adapter ...................... SUCCESS [
>>> 0.082 s]
>>> [INFO] Apache Log4j SLF4J Binding ......................... SUCCESS [
>>> 0.099 s]
>>> [INFO] Apache Log4j SLF4J 1.8+ Binding .................... SUCCESS [
>>> 0.095 s]
>>> [INFO] Apache Log4j Commons Logging Bridge ................ SUCCESS [
>>> 0.092 s]
>>> [INFO] Apache Log4j Flume Bridge .......................... SUCCESS [
>>> 0.090 s]
>>> [INFO] Apache Log4j Web ................................... SUCCESS [
>>> 0.092 s]
>>> [INFO] Apache Log4j Tag Library ........................... SUCCESS [
>>> 0.104 s]
>>> [INFO] Apache Log4j JMX GUI ............................... SUCCESS [
>>> 0.082 s]
>>> [INFO] Apache Log4j Samples ............................... SUCCESS [
>>> 0.113 s]
>>> [INFO] Apache Log4j Samples: Flume - Common ............... SUCCESS [
>>> 0.085 s]
>>> [INFO] Apache Log4j Samples: Flume - Remote ............... SUCCESS [
>>> 0.075 s]
>>> [INFO] Apache Log4j Samples: Flume - Embedded ............. SUCCESS [
>>> 0.079 s]
>>> [INFO] Apache Log4j Samples: Configuration ................ SUCCESS [
>>> 0.069 s]
>>> [INFO] Apache Log4j Samples: LoggerProperties ............. SUCCESS [
>>> 0.084 s]
>>> [INFO] Apache Log4j BOM ................................... SUCCESS [
>>> 0.189 s]
>>> [INFO] Apache Log4j JDBC DBCP 2 ........................... SUCCESS [
>>> 0.069 s]
>>> [INFO] Apache Log4j JPA ................................... SUCCESS [
>>> 0.112 s]
>>> [INFO] Apache Log4j CouchDB ............................... SUCCESS [
>>> 0.073 s]
>>> [INFO] Apache Log4j MongoDB 2 ............................. SUCCESS [
>>> 0.082 s]
>>> [INFO] Apache Log4j MongoDB 3 ............................. SUCCESS [
>>> 0.091 s]
>>> [INFO] Apache Log4j Cassandra ............................. SUCCESS [
>>> 0.076 s]
>>> [INFO] Apache Log4J Performance Tests ..................... SUCCESS [
>>> 0.273 s]
>>> [INFO] Apache Log4j Streaming Interface ................... SUCCESS [
>>> 0.103 s]
>>> [INFO] Apache Log4j JUL Adapter ........................... SUCCESS [
>>> 0.093 s]
>>> [INFO] Apache Log4j Liquibase Binding ..................... SUCCESS [
>>> 0.067 s]
>>> [INFO] Apache Log4j App Server Support .................... SUCCESS [
>>> 0.071 s]
>>> [INFO] Apache Log4j OSGi .................................. SUCCESS [
>>> 0.071 s]
>>> [INFO] Apache Log4j Docker Library ........................ SUCCESS [
>>> 0.081 s]
>>> [INFO] Apache Log4j Spring Cloud Config Support ........... SUCCESS [
>>> 0.110 s]
>>> [INFO] Apache Log4j Spring Cloud Config Client Support .... SUCCESS [
>>> 0.083 s]
>>> [INFO] Log4j Sample Configuration Service ................. FAILURE [
>>> 1.429 s]
>>> [INFO] Apache Log4j Spring Cloud Config Samples ........... SKIPPED
>>> [INFO] Spring Cloud Config Sample Application ............. SKIPPED
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Total time:  10.809 s
>>> [INFO] Finished at: 2019-06-26T08:55:03-04:00
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] No plugin found for prefix 'apache-rat' in the current project
>> and
>>> in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo]
>>> available from the repositories [local
>> (C:\Users\ggregory\.m2\repository),
>>> central (https://repo.maven.apache.org/maven2)] -> [Help 1]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e
>>> switch.
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> [ERROR]
>>> [ERROR] For more information about the errors and possible solutions,
>>> please read the following articles:
>>> [ERROR] [Help 1]
>>> 
>> http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundForPrefixException
>>> 
>>> How does that make any sense?
>>> 
>>> Gary
>>> 
>>> 
>>>> 
>>>> Gary
>>>> 
>>>> On Tue, Jun 25, 2019 at 11:59 PM Ralph Goers <
>> ralph.goers@dslextreme.com>
>>>> wrote:
>>>> 
>>>>> This is a vote to release Log4j 2.12.0, the next version of the Log4j 2
>>>>> project.
>>>>> 
>>>>> Please download, test, and cast your votes on the log4j developers
>> list.
>>>>> [] +1, release the artifacts
>>>>> [] -1, don't release because...
>>>>> 
>>>>> The vote will remain open for 72 hours (or more if required). All votes
>>>>> are welcome and we encourage everyone to test the release, but only
>> Logging
>>>>> PMC votes are “officially” counted. As always, at least 3 +1 votes and
>> more
>>>>> positive than negative votes are required.
>>>>> 
>>>>> Changes in this release include:
>>>>> 
>>>>> New Features
>>>>> 
>>>>>       • LOG4J2-2403: Allow zero padding the counter of a
>>>>> RollingFileAppender. Thanks to hupfdule.
>>>>>       • LOG4J2-2427: Add filter that will match events when no marker
>>>>> is present. Thanks to Rimaljit Kaur.
>>>>>       • LOG4J2-2406: Add reconfiguration methods to Configurator.
>>>>>       • LOG4J2-913: Add support for reconfiguration via HTTP(S),
>>>>> Docker, and Spring Cloud Configuration.
>>>>>       • LOG4J2-2586: TCP Appender should support a host name resolving
>>>>> to multiple IP addresses.
>>>>>       • LOG4J2-2337: Allow custom end-of-line with JsonLayout. Thanks
>>>>> to Arvind Sahare, Patrice Ferrot.
>>>>>       • LOG4J2-2598: GZIP compression on rollover supports
>> configurable
>>>>> compression levels. Thanks to Carter Kozak.
>>>>>       • LOG4J2-2611: AsyncQueueFullPolicy configuration short values
>>>>> "Default" and "Discard" are case insensitive to avoid confusion.
>>>>>       • LOG4J2-2634: Add and use method
>>>>> org.apache.logging.log4j.message.MapMessage.toKey(String) for simpler
>>>>> subclasses.
>>>>> Fixed Bugs
>>>>> 
>>>>>       • LOG4J2-2547: RollingRandomAccessFileAppender error message
>>>>> referenced incorrect class name.
>>>>>       • LOG4J2-2616: Restore constructor to ThrowablePatternConverter
>>>>> that was removed in 2.8.2.
>>>>>       • LOG4J2-2622: StructuredDataId was ignoring maxLength atribute.
>>>>>       • LOG4J2-2636: RFC5424Layout was not properly setting default
>>>>> Structured Element id for the MDC
>>>>>       • LOG4J2-1143: Lookups were not found if the plugin key was not
>>>>> lowercase. Thanks to Pascal Heinrich.
>>>>>       • LOG4J2-1852: Locate plugins within a Jar using a URL
>>>>> Connection. Thanks to Tanner Altares.
>>>>>       • LOG4J2-2610: Explicitly set file creation time.
>>>>>       • LOG4J2-2561: JEP223 version detection fix for JDK 9 and up.
>>>>> Thanks to Ulrich Enslin.
>>>>>       • LOG4J2-1103: FailoverAppender was failing with ERROR appender
>>>>> Failover has no parameter that matches element Failovers. Thanks to
>> Seán
>>>>> Dunne.
>>>>>       • LOG4J2-2602: Update file time when size based triggering
>> policy
>>>>> is used without a time-based triggering policy.
>>>>>       • LOG4J2-2597: Throw better exception message when both
>>>>> log4j-slf4j-impl and log4j-to-slf4j are present.
>>>>>       • LOG4J2-2559: NullPointerException in
>>>>> JdbcAppender.createAppender(). Thanks to Li Lei, Gary Gregory.
>>>>>       • LOG4J2-2592: StackOverflowException when server not reachable
>>>>> with SocketAppender. Thanks to Dávid Kaya, Gary Gregory.
>>>>>       • LOG4J2-2598: java.lang.StackOverflowError at
>>>>> 
>> org.apache.logging.log4j.junit.AbstractExternalFileCleaner.println(AbstractExternalFileCleaner.java:169).
>>>>> Thanks to Gary Gregory.
>>>>>       • LOG4J2-2564: MapPatternConverter is properly created from the
>>>>> '%K', '%map', and '%MAP' patterns. PatternConverter instanceOf methods
>> with
>>>>> unknown parameter types no longer elide those with known parameters.
>>>>>       • LOG4J2-2612: NullPointerException at
>>>>> 
>> org.apache.logging.log4j.core.appender.db.jdbc.JdbcDatabaseManager.writeInternal(JdbcDatabaseManager.java:803).
>>>>>       • LOG4J2-2618: Possible ClassCastException in
>>>>> 
>> org.apache.logging.log4j.core.script.ScriptManager.ScriptManager(Configuration,
>>>>> WatchManager)
>>>>>       • LOG4J2-2631: RoutingAppender PurgePolicy implementations no
>>>>> longer stop appenders referenced from the logger configuration, only
>> those
>>>>> that have been created by the RoutingAppender. Note that
>>>>> RoutingAppender.getAppenders no longer includes entries for referenced
>>>>> appenders, only those which it has created.
>>>>>       • LOG4J2-2629: Fix a race allowing events not to be recorded
>> when
>>>>> a RoutingAppender purge policy attempts to delete an idle appender at
>>>>> exactly the same time as a new event is recorded.
>>>>>       • LOG4J2-2606: Asynchronous logging when the queue is full no
>>>>> longer results in heavy CPU utilization and low throughput.
>>>>> Changes
>>>>> 
>>>>>       • : Update tests from H2 1.4.197 to 1.4.199. Thanks to Gary
>>>>> Gregory.
>>>>>       • LOG4J2-2570: Update Jackson from 2.9.7 to 2.9.8. Thanks to
>> Gary
>>>>> Gregory.
>>>>>       • LOG4J2-2574: Update MongoDB 3 module driver from 3.9.0 to
>>>>> 3.10.1. Thanks to Gary Gregory.
>>>>>       • LOG4J2-2619: Update Jackson from 2.9.8 to 2.9.9.
>>>>>       • LOG4J2-2634: Refactor several AsyncLogger methods below the 35
>>>>> byte threshold for inlining.
>>>>> 
>>>>> Tag:
>>>>> a)  for a new copy do "git clone
>>>>> https://github.com/apache/logging-log4j2.git" and then "git checkout
>>>>> tags/log4j-2.12.0-rc2”
>>>>> b) for an existing working copy to “git pull” and then “git checkout
>>>>> tags/log4j-2.12.0-rc2”
>>>>> 
>>>>> Web Site:  http://rgoers.github.io/log4j2-site/index.html.
>>>>> 
>>>>> Maven Artifacts:
>>>>> 
>> https://repository.apache.org/content/repositories/orgapachelogging-1047
>>>>> 
>>>>> Distribution archives:
>>>>> https://dist.apache.org/repos/dist/dev/logging/log4j/
>>>>> 
>>>>> You may download all the Maven artifacts by executing:
>>>>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
>>>>> 
>> https://repository.apache.org/content/repositories/orgapachelogging-1047/org/apache/logging/log4j/
>>>>> 
>>>>> Ralph
>>>>> 
>>>> 
>> 
>>

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Gary Gregory <ga...@gmail.com>.
On Wed, Jun 26, 2019 at 9:08 AM Ralph Goers <ra...@dslextreme.com>
wrote:

> That is interesting. As part of the pre-release process I run mvn -P rat
> -DskipTests clean verify and that succeeded.
>

Your command works for me as well, no surprise and a good thing. But
replacing '-P rat' with 'apache-rat:check' in that command fails. Weird.

I will keep on testing.

Gary


>
> Ralph
>
> > On Jun 26, 2019, at 5:58 AM, Gary Gregory <ga...@gmail.com>
> wrote:
> >
> > On Wed, Jun 26, 2019 at 8:40 AM Gary Gregory <ga...@gmail.com>
> wrote:
> >
> >> FYI, running 'mvn apache-rat:check' fails on log4j-cassandra/.toDelete
> >>
> >
> > Ah, I can see that we have .gitignore set up to ignore this file so I
> > deleted it and ran 'mvn apache-rat:check' again and got:
> >
> > [INFO] --<
> > org.apache.logging.log4j.samples:log4j-spring-cloud-config-sample-server
> >--
> > [INFO] Building Log4j Sample Configuration Service 2.12.0
> > [38/40]
> > [INFO] --------------------------------[ jar
> > ]---------------------------------
> > [WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is
> > missing, no dependency information available
> > [WARNING] Failed to retrieve plugin descriptor for
> > org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin
> > org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could
> > not be resolved: Failure to find
> > org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 in
> > https://repo.maven.apache.org/maven2 was cached in the local repository,
> > resolution will not be reattempted until the update interval of central
> has
> > elapsed or updates are forced
> > Downloading from central:
> >
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> > Downloading from central:
> >
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
> > Downloaded from central:
> >
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> > (14 kB at 17 kB/s)
> > Downloaded from central:
> >
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
> > (20 kB at 26 kB/s)
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Reactor Summary for Apache Log4j 2 2.12.0:
> > [INFO]
> > [INFO] Apache Log4j 2 ..................................... SUCCESS [
> > 1.859 s]
> > [INFO] Apache Log4j API Java 9 support .................... SUCCESS [
> > 0.125 s]
> > [INFO] Apache Log4j API ................................... SUCCESS [
> > 0.454 s]
> > [INFO] Apache Log4j Implementation Java 9 support ......... SUCCESS [
> > 0.079 s]
> > [INFO] Apache Log4j Core .................................. SUCCESS [
> > 1.183 s]
> > [INFO] Apache Log4j Core Integration Tests ................ SUCCESS [
> > 0.088 s]
> > [INFO] Apache Log4j 1.x Compatibility API ................. SUCCESS [
> > 0.198 s]
> > [INFO] Apache Log4j to SLF4J Adapter ...................... SUCCESS [
> > 0.082 s]
> > [INFO] Apache Log4j SLF4J Binding ......................... SUCCESS [
> > 0.099 s]
> > [INFO] Apache Log4j SLF4J 1.8+ Binding .................... SUCCESS [
> > 0.095 s]
> > [INFO] Apache Log4j Commons Logging Bridge ................ SUCCESS [
> > 0.092 s]
> > [INFO] Apache Log4j Flume Bridge .......................... SUCCESS [
> > 0.090 s]
> > [INFO] Apache Log4j Web ................................... SUCCESS [
> > 0.092 s]
> > [INFO] Apache Log4j Tag Library ........................... SUCCESS [
> > 0.104 s]
> > [INFO] Apache Log4j JMX GUI ............................... SUCCESS [
> > 0.082 s]
> > [INFO] Apache Log4j Samples ............................... SUCCESS [
> > 0.113 s]
> > [INFO] Apache Log4j Samples: Flume - Common ............... SUCCESS [
> > 0.085 s]
> > [INFO] Apache Log4j Samples: Flume - Remote ............... SUCCESS [
> > 0.075 s]
> > [INFO] Apache Log4j Samples: Flume - Embedded ............. SUCCESS [
> > 0.079 s]
> > [INFO] Apache Log4j Samples: Configuration ................ SUCCESS [
> > 0.069 s]
> > [INFO] Apache Log4j Samples: LoggerProperties ............. SUCCESS [
> > 0.084 s]
> > [INFO] Apache Log4j BOM ................................... SUCCESS [
> > 0.189 s]
> > [INFO] Apache Log4j JDBC DBCP 2 ........................... SUCCESS [
> > 0.069 s]
> > [INFO] Apache Log4j JPA ................................... SUCCESS [
> > 0.112 s]
> > [INFO] Apache Log4j CouchDB ............................... SUCCESS [
> > 0.073 s]
> > [INFO] Apache Log4j MongoDB 2 ............................. SUCCESS [
> > 0.082 s]
> > [INFO] Apache Log4j MongoDB 3 ............................. SUCCESS [
> > 0.091 s]
> > [INFO] Apache Log4j Cassandra ............................. SUCCESS [
> > 0.076 s]
> > [INFO] Apache Log4J Performance Tests ..................... SUCCESS [
> > 0.273 s]
> > [INFO] Apache Log4j Streaming Interface ................... SUCCESS [
> > 0.103 s]
> > [INFO] Apache Log4j JUL Adapter ........................... SUCCESS [
> > 0.093 s]
> > [INFO] Apache Log4j Liquibase Binding ..................... SUCCESS [
> > 0.067 s]
> > [INFO] Apache Log4j App Server Support .................... SUCCESS [
> > 0.071 s]
> > [INFO] Apache Log4j OSGi .................................. SUCCESS [
> > 0.071 s]
> > [INFO] Apache Log4j Docker Library ........................ SUCCESS [
> > 0.081 s]
> > [INFO] Apache Log4j Spring Cloud Config Support ........... SUCCESS [
> > 0.110 s]
> > [INFO] Apache Log4j Spring Cloud Config Client Support .... SUCCESS [
> > 0.083 s]
> > [INFO] Log4j Sample Configuration Service ................. FAILURE [
> > 1.429 s]
> > [INFO] Apache Log4j Spring Cloud Config Samples ........... SKIPPED
> > [INFO] Spring Cloud Config Sample Application ............. SKIPPED
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] BUILD FAILURE
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Total time:  10.809 s
> > [INFO] Finished at: 2019-06-26T08:55:03-04:00
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] No plugin found for prefix 'apache-rat' in the current project
> and
> > in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo]
> > available from the repositories [local
> (C:\Users\ggregory\.m2\repository),
> > central (https://repo.maven.apache.org/maven2)] -> [Help 1]
> > [ERROR]
> > [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e
> > switch.
> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> > [ERROR]
> > [ERROR] For more information about the errors and possible solutions,
> > please read the following articles:
> > [ERROR] [Help 1]
> >
> http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundForPrefixException
> >
> > How does that make any sense?
> >
> > Gary
> >
> >
> >>
> >> Gary
> >>
> >> On Tue, Jun 25, 2019 at 11:59 PM Ralph Goers <
> ralph.goers@dslextreme.com>
> >> wrote:
> >>
> >>> This is a vote to release Log4j 2.12.0, the next version of the Log4j 2
> >>> project.
> >>>
> >>> Please download, test, and cast your votes on the log4j developers
> list.
> >>> [] +1, release the artifacts
> >>> [] -1, don't release because...
> >>>
> >>> The vote will remain open for 72 hours (or more if required). All votes
> >>> are welcome and we encourage everyone to test the release, but only
> Logging
> >>> PMC votes are “officially” counted. As always, at least 3 +1 votes and
> more
> >>> positive than negative votes are required.
> >>>
> >>> Changes in this release include:
> >>>
> >>> New Features
> >>>
> >>>        • LOG4J2-2403: Allow zero padding the counter of a
> >>> RollingFileAppender. Thanks to hupfdule.
> >>>        • LOG4J2-2427: Add filter that will match events when no marker
> >>> is present. Thanks to Rimaljit Kaur.
> >>>        • LOG4J2-2406: Add reconfiguration methods to Configurator.
> >>>        • LOG4J2-913: Add support for reconfiguration via HTTP(S),
> >>> Docker, and Spring Cloud Configuration.
> >>>        • LOG4J2-2586: TCP Appender should support a host name resolving
> >>> to multiple IP addresses.
> >>>        • LOG4J2-2337: Allow custom end-of-line with JsonLayout. Thanks
> >>> to Arvind Sahare, Patrice Ferrot.
> >>>        • LOG4J2-2598: GZIP compression on rollover supports
> configurable
> >>> compression levels. Thanks to Carter Kozak.
> >>>        • LOG4J2-2611: AsyncQueueFullPolicy configuration short values
> >>> "Default" and "Discard" are case insensitive to avoid confusion.
> >>>        • LOG4J2-2634: Add and use method
> >>> org.apache.logging.log4j.message.MapMessage.toKey(String) for simpler
> >>> subclasses.
> >>> Fixed Bugs
> >>>
> >>>        • LOG4J2-2547: RollingRandomAccessFileAppender error message
> >>> referenced incorrect class name.
> >>>        • LOG4J2-2616: Restore constructor to ThrowablePatternConverter
> >>> that was removed in 2.8.2.
> >>>        • LOG4J2-2622: StructuredDataId was ignoring maxLength atribute.
> >>>        • LOG4J2-2636: RFC5424Layout was not properly setting default
> >>> Structured Element id for the MDC
> >>>        • LOG4J2-1143: Lookups were not found if the plugin key was not
> >>> lowercase. Thanks to Pascal Heinrich.
> >>>        • LOG4J2-1852: Locate plugins within a Jar using a URL
> >>> Connection. Thanks to Tanner Altares.
> >>>        • LOG4J2-2610: Explicitly set file creation time.
> >>>        • LOG4J2-2561: JEP223 version detection fix for JDK 9 and up.
> >>> Thanks to Ulrich Enslin.
> >>>        • LOG4J2-1103: FailoverAppender was failing with ERROR appender
> >>> Failover has no parameter that matches element Failovers. Thanks to
> Seán
> >>> Dunne.
> >>>        • LOG4J2-2602: Update file time when size based triggering
> policy
> >>> is used without a time-based triggering policy.
> >>>        • LOG4J2-2597: Throw better exception message when both
> >>> log4j-slf4j-impl and log4j-to-slf4j are present.
> >>>        • LOG4J2-2559: NullPointerException in
> >>> JdbcAppender.createAppender(). Thanks to Li Lei, Gary Gregory.
> >>>        • LOG4J2-2592: StackOverflowException when server not reachable
> >>> with SocketAppender. Thanks to Dávid Kaya, Gary Gregory.
> >>>        • LOG4J2-2598: java.lang.StackOverflowError at
> >>>
> org.apache.logging.log4j.junit.AbstractExternalFileCleaner.println(AbstractExternalFileCleaner.java:169).
> >>> Thanks to Gary Gregory.
> >>>        • LOG4J2-2564: MapPatternConverter is properly created from the
> >>> '%K', '%map', and '%MAP' patterns. PatternConverter instanceOf methods
> with
> >>> unknown parameter types no longer elide those with known parameters.
> >>>        • LOG4J2-2612: NullPointerException at
> >>>
> org.apache.logging.log4j.core.appender.db.jdbc.JdbcDatabaseManager.writeInternal(JdbcDatabaseManager.java:803).
> >>>        • LOG4J2-2618: Possible ClassCastException in
> >>>
> org.apache.logging.log4j.core.script.ScriptManager.ScriptManager(Configuration,
> >>> WatchManager)
> >>>        • LOG4J2-2631: RoutingAppender PurgePolicy implementations no
> >>> longer stop appenders referenced from the logger configuration, only
> those
> >>> that have been created by the RoutingAppender. Note that
> >>> RoutingAppender.getAppenders no longer includes entries for referenced
> >>> appenders, only those which it has created.
> >>>        • LOG4J2-2629: Fix a race allowing events not to be recorded
> when
> >>> a RoutingAppender purge policy attempts to delete an idle appender at
> >>> exactly the same time as a new event is recorded.
> >>>        • LOG4J2-2606: Asynchronous logging when the queue is full no
> >>> longer results in heavy CPU utilization and low throughput.
> >>> Changes
> >>>
> >>>        • : Update tests from H2 1.4.197 to 1.4.199. Thanks to Gary
> >>> Gregory.
> >>>        • LOG4J2-2570: Update Jackson from 2.9.7 to 2.9.8. Thanks to
> Gary
> >>> Gregory.
> >>>        • LOG4J2-2574: Update MongoDB 3 module driver from 3.9.0 to
> >>> 3.10.1. Thanks to Gary Gregory.
> >>>        • LOG4J2-2619: Update Jackson from 2.9.8 to 2.9.9.
> >>>        • LOG4J2-2634: Refactor several AsyncLogger methods below the 35
> >>> byte threshold for inlining.
> >>>
> >>> Tag:
> >>> a)  for a new copy do "git clone
> >>> https://github.com/apache/logging-log4j2.git" and then "git checkout
> >>> tags/log4j-2.12.0-rc2”
> >>> b) for an existing working copy to “git pull” and then “git checkout
> >>> tags/log4j-2.12.0-rc2”
> >>>
> >>> Web Site:  http://rgoers.github.io/log4j2-site/index.html.
> >>>
> >>> Maven Artifacts:
> >>>
> https://repository.apache.org/content/repositories/orgapachelogging-1047
> >>>
> >>> Distribution archives:
> >>> https://dist.apache.org/repos/dist/dev/logging/log4j/
> >>>
> >>> You may download all the Maven artifacts by executing:
> >>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
> >>>
> https://repository.apache.org/content/repositories/orgapachelogging-1047/org/apache/logging/log4j/
> >>>
> >>> Ralph
> >>>
> >>
>
>

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Ralph Goers <ra...@dslextreme.com>.
That is interesting. As part of the pre-release process I run mvn -P rat -DskipTests clean verify and that succeeded.

Ralph

> On Jun 26, 2019, at 5:58 AM, Gary Gregory <ga...@gmail.com> wrote:
> 
> On Wed, Jun 26, 2019 at 8:40 AM Gary Gregory <ga...@gmail.com> wrote:
> 
>> FYI, running 'mvn apache-rat:check' fails on log4j-cassandra/.toDelete
>> 
> 
> Ah, I can see that we have .gitignore set up to ignore this file so I
> deleted it and ran 'mvn apache-rat:check' again and got:
> 
> [INFO] --<
> org.apache.logging.log4j.samples:log4j-spring-cloud-config-sample-server >--
> [INFO] Building Log4j Sample Configuration Service 2.12.0
> [38/40]
> [INFO] --------------------------------[ jar
> ]---------------------------------
> [WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is
> missing, no dependency information available
> [WARNING] Failed to retrieve plugin descriptor for
> org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin
> org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could
> not be resolved: Failure to find
> org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> (14 kB at 17 kB/s)
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
> (20 kB at 26 kB/s)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary for Apache Log4j 2 2.12.0:
> [INFO]
> [INFO] Apache Log4j 2 ..................................... SUCCESS [
> 1.859 s]
> [INFO] Apache Log4j API Java 9 support .................... SUCCESS [
> 0.125 s]
> [INFO] Apache Log4j API ................................... SUCCESS [
> 0.454 s]
> [INFO] Apache Log4j Implementation Java 9 support ......... SUCCESS [
> 0.079 s]
> [INFO] Apache Log4j Core .................................. SUCCESS [
> 1.183 s]
> [INFO] Apache Log4j Core Integration Tests ................ SUCCESS [
> 0.088 s]
> [INFO] Apache Log4j 1.x Compatibility API ................. SUCCESS [
> 0.198 s]
> [INFO] Apache Log4j to SLF4J Adapter ...................... SUCCESS [
> 0.082 s]
> [INFO] Apache Log4j SLF4J Binding ......................... SUCCESS [
> 0.099 s]
> [INFO] Apache Log4j SLF4J 1.8+ Binding .................... SUCCESS [
> 0.095 s]
> [INFO] Apache Log4j Commons Logging Bridge ................ SUCCESS [
> 0.092 s]
> [INFO] Apache Log4j Flume Bridge .......................... SUCCESS [
> 0.090 s]
> [INFO] Apache Log4j Web ................................... SUCCESS [
> 0.092 s]
> [INFO] Apache Log4j Tag Library ........................... SUCCESS [
> 0.104 s]
> [INFO] Apache Log4j JMX GUI ............................... SUCCESS [
> 0.082 s]
> [INFO] Apache Log4j Samples ............................... SUCCESS [
> 0.113 s]
> [INFO] Apache Log4j Samples: Flume - Common ............... SUCCESS [
> 0.085 s]
> [INFO] Apache Log4j Samples: Flume - Remote ............... SUCCESS [
> 0.075 s]
> [INFO] Apache Log4j Samples: Flume - Embedded ............. SUCCESS [
> 0.079 s]
> [INFO] Apache Log4j Samples: Configuration ................ SUCCESS [
> 0.069 s]
> [INFO] Apache Log4j Samples: LoggerProperties ............. SUCCESS [
> 0.084 s]
> [INFO] Apache Log4j BOM ................................... SUCCESS [
> 0.189 s]
> [INFO] Apache Log4j JDBC DBCP 2 ........................... SUCCESS [
> 0.069 s]
> [INFO] Apache Log4j JPA ................................... SUCCESS [
> 0.112 s]
> [INFO] Apache Log4j CouchDB ............................... SUCCESS [
> 0.073 s]
> [INFO] Apache Log4j MongoDB 2 ............................. SUCCESS [
> 0.082 s]
> [INFO] Apache Log4j MongoDB 3 ............................. SUCCESS [
> 0.091 s]
> [INFO] Apache Log4j Cassandra ............................. SUCCESS [
> 0.076 s]
> [INFO] Apache Log4J Performance Tests ..................... SUCCESS [
> 0.273 s]
> [INFO] Apache Log4j Streaming Interface ................... SUCCESS [
> 0.103 s]
> [INFO] Apache Log4j JUL Adapter ........................... SUCCESS [
> 0.093 s]
> [INFO] Apache Log4j Liquibase Binding ..................... SUCCESS [
> 0.067 s]
> [INFO] Apache Log4j App Server Support .................... SUCCESS [
> 0.071 s]
> [INFO] Apache Log4j OSGi .................................. SUCCESS [
> 0.071 s]
> [INFO] Apache Log4j Docker Library ........................ SUCCESS [
> 0.081 s]
> [INFO] Apache Log4j Spring Cloud Config Support ........... SUCCESS [
> 0.110 s]
> [INFO] Apache Log4j Spring Cloud Config Client Support .... SUCCESS [
> 0.083 s]
> [INFO] Log4j Sample Configuration Service ................. FAILURE [
> 1.429 s]
> [INFO] Apache Log4j Spring Cloud Config Samples ........... SKIPPED
> [INFO] Spring Cloud Config Sample Application ............. SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time:  10.809 s
> [INFO] Finished at: 2019-06-26T08:55:03-04:00
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] No plugin found for prefix 'apache-rat' in the current project and
> in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo]
> available from the repositories [local (C:\Users\ggregory\.m2\repository),
> central (https://repo.maven.apache.org/maven2)] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundForPrefixException
> 
> How does that make any sense?
> 
> Gary
> 
> 
>> 
>> Gary
>> 
>> On Tue, Jun 25, 2019 at 11:59 PM Ralph Goers <ra...@dslextreme.com>
>> wrote:
>> 
>>> This is a vote to release Log4j 2.12.0, the next version of the Log4j 2
>>> project.
>>> 
>>> Please download, test, and cast your votes on the log4j developers list.
>>> [] +1, release the artifacts
>>> [] -1, don't release because...
>>> 
>>> The vote will remain open for 72 hours (or more if required). All votes
>>> are welcome and we encourage everyone to test the release, but only Logging
>>> PMC votes are “officially” counted. As always, at least 3 +1 votes and more
>>> positive than negative votes are required.
>>> 
>>> Changes in this release include:
>>> 
>>> New Features
>>> 
>>>        • LOG4J2-2403: Allow zero padding the counter of a
>>> RollingFileAppender. Thanks to hupfdule.
>>>        • LOG4J2-2427: Add filter that will match events when no marker
>>> is present. Thanks to Rimaljit Kaur.
>>>        • LOG4J2-2406: Add reconfiguration methods to Configurator.
>>>        • LOG4J2-913: Add support for reconfiguration via HTTP(S),
>>> Docker, and Spring Cloud Configuration.
>>>        • LOG4J2-2586: TCP Appender should support a host name resolving
>>> to multiple IP addresses.
>>>        • LOG4J2-2337: Allow custom end-of-line with JsonLayout. Thanks
>>> to Arvind Sahare, Patrice Ferrot.
>>>        • LOG4J2-2598: GZIP compression on rollover supports configurable
>>> compression levels. Thanks to Carter Kozak.
>>>        • LOG4J2-2611: AsyncQueueFullPolicy configuration short values
>>> "Default" and "Discard" are case insensitive to avoid confusion.
>>>        • LOG4J2-2634: Add and use method
>>> org.apache.logging.log4j.message.MapMessage.toKey(String) for simpler
>>> subclasses.
>>> Fixed Bugs
>>> 
>>>        • LOG4J2-2547: RollingRandomAccessFileAppender error message
>>> referenced incorrect class name.
>>>        • LOG4J2-2616: Restore constructor to ThrowablePatternConverter
>>> that was removed in 2.8.2.
>>>        • LOG4J2-2622: StructuredDataId was ignoring maxLength atribute.
>>>        • LOG4J2-2636: RFC5424Layout was not properly setting default
>>> Structured Element id for the MDC
>>>        • LOG4J2-1143: Lookups were not found if the plugin key was not
>>> lowercase. Thanks to Pascal Heinrich.
>>>        • LOG4J2-1852: Locate plugins within a Jar using a URL
>>> Connection. Thanks to Tanner Altares.
>>>        • LOG4J2-2610: Explicitly set file creation time.
>>>        • LOG4J2-2561: JEP223 version detection fix for JDK 9 and up.
>>> Thanks to Ulrich Enslin.
>>>        • LOG4J2-1103: FailoverAppender was failing with ERROR appender
>>> Failover has no parameter that matches element Failovers. Thanks to Seán
>>> Dunne.
>>>        • LOG4J2-2602: Update file time when size based triggering policy
>>> is used without a time-based triggering policy.
>>>        • LOG4J2-2597: Throw better exception message when both
>>> log4j-slf4j-impl and log4j-to-slf4j are present.
>>>        • LOG4J2-2559: NullPointerException in
>>> JdbcAppender.createAppender(). Thanks to Li Lei, Gary Gregory.
>>>        • LOG4J2-2592: StackOverflowException when server not reachable
>>> with SocketAppender. Thanks to Dávid Kaya, Gary Gregory.
>>>        • LOG4J2-2598: java.lang.StackOverflowError at
>>> org.apache.logging.log4j.junit.AbstractExternalFileCleaner.println(AbstractExternalFileCleaner.java:169).
>>> Thanks to Gary Gregory.
>>>        • LOG4J2-2564: MapPatternConverter is properly created from the
>>> '%K', '%map', and '%MAP' patterns. PatternConverter instanceOf methods with
>>> unknown parameter types no longer elide those with known parameters.
>>>        • LOG4J2-2612: NullPointerException at
>>> org.apache.logging.log4j.core.appender.db.jdbc.JdbcDatabaseManager.writeInternal(JdbcDatabaseManager.java:803).
>>>        • LOG4J2-2618: Possible ClassCastException in
>>> org.apache.logging.log4j.core.script.ScriptManager.ScriptManager(Configuration,
>>> WatchManager)
>>>        • LOG4J2-2631: RoutingAppender PurgePolicy implementations no
>>> longer stop appenders referenced from the logger configuration, only those
>>> that have been created by the RoutingAppender. Note that
>>> RoutingAppender.getAppenders no longer includes entries for referenced
>>> appenders, only those which it has created.
>>>        • LOG4J2-2629: Fix a race allowing events not to be recorded when
>>> a RoutingAppender purge policy attempts to delete an idle appender at
>>> exactly the same time as a new event is recorded.
>>>        • LOG4J2-2606: Asynchronous logging when the queue is full no
>>> longer results in heavy CPU utilization and low throughput.
>>> Changes
>>> 
>>>        • : Update tests from H2 1.4.197 to 1.4.199. Thanks to Gary
>>> Gregory.
>>>        • LOG4J2-2570: Update Jackson from 2.9.7 to 2.9.8. Thanks to Gary
>>> Gregory.
>>>        • LOG4J2-2574: Update MongoDB 3 module driver from 3.9.0 to
>>> 3.10.1. Thanks to Gary Gregory.
>>>        • LOG4J2-2619: Update Jackson from 2.9.8 to 2.9.9.
>>>        • LOG4J2-2634: Refactor several AsyncLogger methods below the 35
>>> byte threshold for inlining.
>>> 
>>> Tag:
>>> a)  for a new copy do "git clone
>>> https://github.com/apache/logging-log4j2.git" and then "git checkout
>>> tags/log4j-2.12.0-rc2”
>>> b) for an existing working copy to “git pull” and then “git checkout
>>> tags/log4j-2.12.0-rc2”
>>> 
>>> Web Site:  http://rgoers.github.io/log4j2-site/index.html.
>>> 
>>> Maven Artifacts:
>>> https://repository.apache.org/content/repositories/orgapachelogging-1047
>>> 
>>> Distribution archives:
>>> https://dist.apache.org/repos/dist/dev/logging/log4j/
>>> 
>>> You may download all the Maven artifacts by executing:
>>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
>>> https://repository.apache.org/content/repositories/orgapachelogging-1047/org/apache/logging/log4j/
>>> 
>>> Ralph
>>> 
>>

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Gary Gregory <ga...@gmail.com>.
Please note these nits as TODOs, the following Maven module descriptions
should start with "Apache Log4j" like all the other modules:

[INFO] Log4j Sample Configuration Service ................. FAILURE [
 1.429 s]
[INFO] Spring Cloud Config Sample Application ............. SKIPPED

Gary


On Wed, Jun 26, 2019 at 8:58 AM Gary Gregory <ga...@gmail.com> wrote:

> On Wed, Jun 26, 2019 at 8:40 AM Gary Gregory <ga...@gmail.com>
> wrote:
>
>> FYI, running 'mvn apache-rat:check' fails on log4j-cassandra/.toDelete
>>
>
> Ah, I can see that we have .gitignore set up to ignore this file so I
> deleted it and ran 'mvn apache-rat:check' again and got:
>
> [INFO] --<
> org.apache.logging.log4j.samples:log4j-spring-cloud-config-sample-server >--
> [INFO] Building Log4j Sample Configuration Service 2.12.0
> [38/40]
> [INFO] --------------------------------[ jar
> ]---------------------------------
> [WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is
> missing, no dependency information available
> [WARNING] Failed to retrieve plugin descriptor for
> org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin
> org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could
> not be resolved: Failure to find
> org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> (14 kB at 17 kB/s)
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
> (20 kB at 26 kB/s)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary for Apache Log4j 2 2.12.0:
> [INFO]
> [INFO] Apache Log4j 2 ..................................... SUCCESS [
>  1.859 s]
> [INFO] Apache Log4j API Java 9 support .................... SUCCESS [
>  0.125 s]
> [INFO] Apache Log4j API ................................... SUCCESS [
>  0.454 s]
> [INFO] Apache Log4j Implementation Java 9 support ......... SUCCESS [
>  0.079 s]
> [INFO] Apache Log4j Core .................................. SUCCESS [
>  1.183 s]
> [INFO] Apache Log4j Core Integration Tests ................ SUCCESS [
>  0.088 s]
> [INFO] Apache Log4j 1.x Compatibility API ................. SUCCESS [
>  0.198 s]
> [INFO] Apache Log4j to SLF4J Adapter ...................... SUCCESS [
>  0.082 s]
> [INFO] Apache Log4j SLF4J Binding ......................... SUCCESS [
>  0.099 s]
> [INFO] Apache Log4j SLF4J 1.8+ Binding .................... SUCCESS [
>  0.095 s]
> [INFO] Apache Log4j Commons Logging Bridge ................ SUCCESS [
>  0.092 s]
> [INFO] Apache Log4j Flume Bridge .......................... SUCCESS [
>  0.090 s]
> [INFO] Apache Log4j Web ................................... SUCCESS [
>  0.092 s]
> [INFO] Apache Log4j Tag Library ........................... SUCCESS [
>  0.104 s]
> [INFO] Apache Log4j JMX GUI ............................... SUCCESS [
>  0.082 s]
> [INFO] Apache Log4j Samples ............................... SUCCESS [
>  0.113 s]
> [INFO] Apache Log4j Samples: Flume - Common ............... SUCCESS [
>  0.085 s]
> [INFO] Apache Log4j Samples: Flume - Remote ............... SUCCESS [
>  0.075 s]
> [INFO] Apache Log4j Samples: Flume - Embedded ............. SUCCESS [
>  0.079 s]
> [INFO] Apache Log4j Samples: Configuration ................ SUCCESS [
>  0.069 s]
> [INFO] Apache Log4j Samples: LoggerProperties ............. SUCCESS [
>  0.084 s]
> [INFO] Apache Log4j BOM ................................... SUCCESS [
>  0.189 s]
> [INFO] Apache Log4j JDBC DBCP 2 ........................... SUCCESS [
>  0.069 s]
> [INFO] Apache Log4j JPA ................................... SUCCESS [
>  0.112 s]
> [INFO] Apache Log4j CouchDB ............................... SUCCESS [
>  0.073 s]
> [INFO] Apache Log4j MongoDB 2 ............................. SUCCESS [
>  0.082 s]
> [INFO] Apache Log4j MongoDB 3 ............................. SUCCESS [
>  0.091 s]
> [INFO] Apache Log4j Cassandra ............................. SUCCESS [
>  0.076 s]
> [INFO] Apache Log4J Performance Tests ..................... SUCCESS [
>  0.273 s]
> [INFO] Apache Log4j Streaming Interface ................... SUCCESS [
>  0.103 s]
> [INFO] Apache Log4j JUL Adapter ........................... SUCCESS [
>  0.093 s]
> [INFO] Apache Log4j Liquibase Binding ..................... SUCCESS [
>  0.067 s]
> [INFO] Apache Log4j App Server Support .................... SUCCESS [
>  0.071 s]
> [INFO] Apache Log4j OSGi .................................. SUCCESS [
>  0.071 s]
> [INFO] Apache Log4j Docker Library ........................ SUCCESS [
>  0.081 s]
> [INFO] Apache Log4j Spring Cloud Config Support ........... SUCCESS [
>  0.110 s]
> [INFO] Apache Log4j Spring Cloud Config Client Support .... SUCCESS [
>  0.083 s]
> [INFO] Log4j Sample Configuration Service ................. FAILURE [
>  1.429 s]
> [INFO] Apache Log4j Spring Cloud Config Samples ........... SKIPPED
> [INFO] Spring Cloud Config Sample Application ............. SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time:  10.809 s
> [INFO] Finished at: 2019-06-26T08:55:03-04:00
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] No plugin found for prefix 'apache-rat' in the current project and
> in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo]
> available from the repositories [local (C:\Users\ggregory\.m2\repository),
> central (https://repo.maven.apache.org/maven2)] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundForPrefixException
>
> How does that make any sense?
>
> Gary
>
>
>>
>> Gary
>>
>> On Tue, Jun 25, 2019 at 11:59 PM Ralph Goers <ra...@dslextreme.com>
>> wrote:
>>
>>> This is a vote to release Log4j 2.12.0, the next version of the Log4j 2
>>> project.
>>>
>>> Please download, test, and cast your votes on the log4j developers list.
>>> [] +1, release the artifacts
>>> [] -1, don't release because...
>>>
>>> The vote will remain open for 72 hours (or more if required). All votes
>>> are welcome and we encourage everyone to test the release, but only Logging
>>> PMC votes are “officially” counted. As always, at least 3 +1 votes and more
>>> positive than negative votes are required.
>>>
>>> Changes in this release include:
>>>
>>> New Features
>>>
>>>         • LOG4J2-2403: Allow zero padding the counter of a
>>> RollingFileAppender. Thanks to hupfdule.
>>>         • LOG4J2-2427: Add filter that will match events when no marker
>>> is present. Thanks to Rimaljit Kaur.
>>>         • LOG4J2-2406: Add reconfiguration methods to Configurator.
>>>         • LOG4J2-913: Add support for reconfiguration via HTTP(S),
>>> Docker, and Spring Cloud Configuration.
>>>         • LOG4J2-2586: TCP Appender should support a host name resolving
>>> to multiple IP addresses.
>>>         • LOG4J2-2337: Allow custom end-of-line with JsonLayout. Thanks
>>> to Arvind Sahare, Patrice Ferrot.
>>>         • LOG4J2-2598: GZIP compression on rollover supports
>>> configurable compression levels. Thanks to Carter Kozak.
>>>         • LOG4J2-2611: AsyncQueueFullPolicy configuration short values
>>> "Default" and "Discard" are case insensitive to avoid confusion.
>>>         • LOG4J2-2634: Add and use method
>>> org.apache.logging.log4j.message.MapMessage.toKey(String) for simpler
>>> subclasses.
>>> Fixed Bugs
>>>
>>>         • LOG4J2-2547: RollingRandomAccessFileAppender error message
>>> referenced incorrect class name.
>>>         • LOG4J2-2616: Restore constructor to ThrowablePatternConverter
>>> that was removed in 2.8.2.
>>>         • LOG4J2-2622: StructuredDataId was ignoring maxLength atribute.
>>>         • LOG4J2-2636: RFC5424Layout was not properly setting default
>>> Structured Element id for the MDC
>>>         • LOG4J2-1143: Lookups were not found if the plugin key was not
>>> lowercase. Thanks to Pascal Heinrich.
>>>         • LOG4J2-1852: Locate plugins within a Jar using a URL
>>> Connection. Thanks to Tanner Altares.
>>>         • LOG4J2-2610: Explicitly set file creation time.
>>>         • LOG4J2-2561: JEP223 version detection fix for JDK 9 and up.
>>> Thanks to Ulrich Enslin.
>>>         • LOG4J2-1103: FailoverAppender was failing with ERROR appender
>>> Failover has no parameter that matches element Failovers. Thanks to Seán
>>> Dunne.
>>>         • LOG4J2-2602: Update file time when size based triggering
>>> policy is used without a time-based triggering policy.
>>>         • LOG4J2-2597: Throw better exception message when both
>>> log4j-slf4j-impl and log4j-to-slf4j are present.
>>>         • LOG4J2-2559: NullPointerException in
>>> JdbcAppender.createAppender(). Thanks to Li Lei, Gary Gregory.
>>>         • LOG4J2-2592: StackOverflowException when server not reachable
>>> with SocketAppender. Thanks to Dávid Kaya, Gary Gregory.
>>>         • LOG4J2-2598: java.lang.StackOverflowError at
>>> org.apache.logging.log4j.junit.AbstractExternalFileCleaner.println(AbstractExternalFileCleaner.java:169).
>>> Thanks to Gary Gregory.
>>>         • LOG4J2-2564: MapPatternConverter is properly created from the
>>> '%K', '%map', and '%MAP' patterns. PatternConverter instanceOf methods with
>>> unknown parameter types no longer elide those with known parameters.
>>>         • LOG4J2-2612: NullPointerException at
>>> org.apache.logging.log4j.core.appender.db.jdbc.JdbcDatabaseManager.writeInternal(JdbcDatabaseManager.java:803).
>>>         • LOG4J2-2618: Possible ClassCastException in
>>> org.apache.logging.log4j.core.script.ScriptManager.ScriptManager(Configuration,
>>> WatchManager)
>>>         • LOG4J2-2631: RoutingAppender PurgePolicy implementations no
>>> longer stop appenders referenced from the logger configuration, only those
>>> that have been created by the RoutingAppender. Note that
>>> RoutingAppender.getAppenders no longer includes entries for referenced
>>> appenders, only those which it has created.
>>>         • LOG4J2-2629: Fix a race allowing events not to be recorded
>>> when a RoutingAppender purge policy attempts to delete an idle appender at
>>> exactly the same time as a new event is recorded.
>>>         • LOG4J2-2606: Asynchronous logging when the queue is full no
>>> longer results in heavy CPU utilization and low throughput.
>>> Changes
>>>
>>>         • : Update tests from H2 1.4.197 to 1.4.199. Thanks to Gary
>>> Gregory.
>>>         • LOG4J2-2570: Update Jackson from 2.9.7 to 2.9.8. Thanks to
>>> Gary Gregory.
>>>         • LOG4J2-2574: Update MongoDB 3 module driver from 3.9.0 to
>>> 3.10.1. Thanks to Gary Gregory.
>>>         • LOG4J2-2619: Update Jackson from 2.9.8 to 2.9.9.
>>>         • LOG4J2-2634: Refactor several AsyncLogger methods below the 35
>>> byte threshold for inlining.
>>>
>>> Tag:
>>> a)  for a new copy do "git clone
>>> https://github.com/apache/logging-log4j2.git" and then "git checkout
>>> tags/log4j-2.12.0-rc2”
>>> b) for an existing working copy to “git pull” and then “git checkout
>>> tags/log4j-2.12.0-rc2”
>>>
>>> Web Site:  http://rgoers.github.io/log4j2-site/index.html.
>>>
>>> Maven Artifacts:
>>> https://repository.apache.org/content/repositories/orgapachelogging-1047
>>>
>>> Distribution archives:
>>> https://dist.apache.org/repos/dist/dev/logging/log4j/
>>>
>>> You may download all the Maven artifacts by executing:
>>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
>>> https://repository.apache.org/content/repositories/orgapachelogging-1047/org/apache/logging/log4j/
>>>
>>> Ralph
>>>
>>

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Gary Gregory <ga...@gmail.com>.
On Wed, Jun 26, 2019 at 8:40 AM Gary Gregory <ga...@gmail.com> wrote:

> FYI, running 'mvn apache-rat:check' fails on log4j-cassandra/.toDelete
>

Ah, I can see that we have .gitignore set up to ignore this file so I
deleted it and ran 'mvn apache-rat:check' again and got:

[INFO] --<
org.apache.logging.log4j.samples:log4j-spring-cloud-config-sample-server >--
[INFO] Building Log4j Sample Configuration Service 2.12.0
[38/40]
[INFO] --------------------------------[ jar
]---------------------------------
[WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is
missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for
org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin
org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could
not be resolved: Failure to find
org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 in
https://repo.maven.apache.org/maven2 was cached in the local repository,
resolution will not be reattempted until the update interval of central has
elapsed or updates are forced
Downloading from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
Downloading from central:
https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
Downloaded from central:
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
(14 kB at 17 kB/s)
Downloaded from central:
https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
(20 kB at 26 kB/s)
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary for Apache Log4j 2 2.12.0:
[INFO]
[INFO] Apache Log4j 2 ..................................... SUCCESS [
 1.859 s]
[INFO] Apache Log4j API Java 9 support .................... SUCCESS [
 0.125 s]
[INFO] Apache Log4j API ................................... SUCCESS [
 0.454 s]
[INFO] Apache Log4j Implementation Java 9 support ......... SUCCESS [
 0.079 s]
[INFO] Apache Log4j Core .................................. SUCCESS [
 1.183 s]
[INFO] Apache Log4j Core Integration Tests ................ SUCCESS [
 0.088 s]
[INFO] Apache Log4j 1.x Compatibility API ................. SUCCESS [
 0.198 s]
[INFO] Apache Log4j to SLF4J Adapter ...................... SUCCESS [
 0.082 s]
[INFO] Apache Log4j SLF4J Binding ......................... SUCCESS [
 0.099 s]
[INFO] Apache Log4j SLF4J 1.8+ Binding .................... SUCCESS [
 0.095 s]
[INFO] Apache Log4j Commons Logging Bridge ................ SUCCESS [
 0.092 s]
[INFO] Apache Log4j Flume Bridge .......................... SUCCESS [
 0.090 s]
[INFO] Apache Log4j Web ................................... SUCCESS [
 0.092 s]
[INFO] Apache Log4j Tag Library ........................... SUCCESS [
 0.104 s]
[INFO] Apache Log4j JMX GUI ............................... SUCCESS [
 0.082 s]
[INFO] Apache Log4j Samples ............................... SUCCESS [
 0.113 s]
[INFO] Apache Log4j Samples: Flume - Common ............... SUCCESS [
 0.085 s]
[INFO] Apache Log4j Samples: Flume - Remote ............... SUCCESS [
 0.075 s]
[INFO] Apache Log4j Samples: Flume - Embedded ............. SUCCESS [
 0.079 s]
[INFO] Apache Log4j Samples: Configuration ................ SUCCESS [
 0.069 s]
[INFO] Apache Log4j Samples: LoggerProperties ............. SUCCESS [
 0.084 s]
[INFO] Apache Log4j BOM ................................... SUCCESS [
 0.189 s]
[INFO] Apache Log4j JDBC DBCP 2 ........................... SUCCESS [
 0.069 s]
[INFO] Apache Log4j JPA ................................... SUCCESS [
 0.112 s]
[INFO] Apache Log4j CouchDB ............................... SUCCESS [
 0.073 s]
[INFO] Apache Log4j MongoDB 2 ............................. SUCCESS [
 0.082 s]
[INFO] Apache Log4j MongoDB 3 ............................. SUCCESS [
 0.091 s]
[INFO] Apache Log4j Cassandra ............................. SUCCESS [
 0.076 s]
[INFO] Apache Log4J Performance Tests ..................... SUCCESS [
 0.273 s]
[INFO] Apache Log4j Streaming Interface ................... SUCCESS [
 0.103 s]
[INFO] Apache Log4j JUL Adapter ........................... SUCCESS [
 0.093 s]
[INFO] Apache Log4j Liquibase Binding ..................... SUCCESS [
 0.067 s]
[INFO] Apache Log4j App Server Support .................... SUCCESS [
 0.071 s]
[INFO] Apache Log4j OSGi .................................. SUCCESS [
 0.071 s]
[INFO] Apache Log4j Docker Library ........................ SUCCESS [
 0.081 s]
[INFO] Apache Log4j Spring Cloud Config Support ........... SUCCESS [
 0.110 s]
[INFO] Apache Log4j Spring Cloud Config Client Support .... SUCCESS [
 0.083 s]
[INFO] Log4j Sample Configuration Service ................. FAILURE [
 1.429 s]
[INFO] Apache Log4j Spring Cloud Config Samples ........... SKIPPED
[INFO] Spring Cloud Config Sample Application ............. SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time:  10.809 s
[INFO] Finished at: 2019-06-26T08:55:03-04:00
[INFO]
------------------------------------------------------------------------
[ERROR] No plugin found for prefix 'apache-rat' in the current project and
in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo]
available from the repositories [local (C:\Users\ggregory\.m2\repository),
central (https://repo.maven.apache.org/maven2)] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundForPrefixException

How does that make any sense?

Gary


>
> Gary
>
> On Tue, Jun 25, 2019 at 11:59 PM Ralph Goers <ra...@dslextreme.com>
> wrote:
>
>> This is a vote to release Log4j 2.12.0, the next version of the Log4j 2
>> project.
>>
>> Please download, test, and cast your votes on the log4j developers list.
>> [] +1, release the artifacts
>> [] -1, don't release because...
>>
>> The vote will remain open for 72 hours (or more if required). All votes
>> are welcome and we encourage everyone to test the release, but only Logging
>> PMC votes are “officially” counted. As always, at least 3 +1 votes and more
>> positive than negative votes are required.
>>
>> Changes in this release include:
>>
>> New Features
>>
>>         • LOG4J2-2403: Allow zero padding the counter of a
>> RollingFileAppender. Thanks to hupfdule.
>>         • LOG4J2-2427: Add filter that will match events when no marker
>> is present. Thanks to Rimaljit Kaur.
>>         • LOG4J2-2406: Add reconfiguration methods to Configurator.
>>         • LOG4J2-913: Add support for reconfiguration via HTTP(S),
>> Docker, and Spring Cloud Configuration.
>>         • LOG4J2-2586: TCP Appender should support a host name resolving
>> to multiple IP addresses.
>>         • LOG4J2-2337: Allow custom end-of-line with JsonLayout. Thanks
>> to Arvind Sahare, Patrice Ferrot.
>>         • LOG4J2-2598: GZIP compression on rollover supports configurable
>> compression levels. Thanks to Carter Kozak.
>>         • LOG4J2-2611: AsyncQueueFullPolicy configuration short values
>> "Default" and "Discard" are case insensitive to avoid confusion.
>>         • LOG4J2-2634: Add and use method
>> org.apache.logging.log4j.message.MapMessage.toKey(String) for simpler
>> subclasses.
>> Fixed Bugs
>>
>>         • LOG4J2-2547: RollingRandomAccessFileAppender error message
>> referenced incorrect class name.
>>         • LOG4J2-2616: Restore constructor to ThrowablePatternConverter
>> that was removed in 2.8.2.
>>         • LOG4J2-2622: StructuredDataId was ignoring maxLength atribute.
>>         • LOG4J2-2636: RFC5424Layout was not properly setting default
>> Structured Element id for the MDC
>>         • LOG4J2-1143: Lookups were not found if the plugin key was not
>> lowercase. Thanks to Pascal Heinrich.
>>         • LOG4J2-1852: Locate plugins within a Jar using a URL
>> Connection. Thanks to Tanner Altares.
>>         • LOG4J2-2610: Explicitly set file creation time.
>>         • LOG4J2-2561: JEP223 version detection fix for JDK 9 and up.
>> Thanks to Ulrich Enslin.
>>         • LOG4J2-1103: FailoverAppender was failing with ERROR appender
>> Failover has no parameter that matches element Failovers. Thanks to Seán
>> Dunne.
>>         • LOG4J2-2602: Update file time when size based triggering policy
>> is used without a time-based triggering policy.
>>         • LOG4J2-2597: Throw better exception message when both
>> log4j-slf4j-impl and log4j-to-slf4j are present.
>>         • LOG4J2-2559: NullPointerException in
>> JdbcAppender.createAppender(). Thanks to Li Lei, Gary Gregory.
>>         • LOG4J2-2592: StackOverflowException when server not reachable
>> with SocketAppender. Thanks to Dávid Kaya, Gary Gregory.
>>         • LOG4J2-2598: java.lang.StackOverflowError at
>> org.apache.logging.log4j.junit.AbstractExternalFileCleaner.println(AbstractExternalFileCleaner.java:169).
>> Thanks to Gary Gregory.
>>         • LOG4J2-2564: MapPatternConverter is properly created from the
>> '%K', '%map', and '%MAP' patterns. PatternConverter instanceOf methods with
>> unknown parameter types no longer elide those with known parameters.
>>         • LOG4J2-2612: NullPointerException at
>> org.apache.logging.log4j.core.appender.db.jdbc.JdbcDatabaseManager.writeInternal(JdbcDatabaseManager.java:803).
>>         • LOG4J2-2618: Possible ClassCastException in
>> org.apache.logging.log4j.core.script.ScriptManager.ScriptManager(Configuration,
>> WatchManager)
>>         • LOG4J2-2631: RoutingAppender PurgePolicy implementations no
>> longer stop appenders referenced from the logger configuration, only those
>> that have been created by the RoutingAppender. Note that
>> RoutingAppender.getAppenders no longer includes entries for referenced
>> appenders, only those which it has created.
>>         • LOG4J2-2629: Fix a race allowing events not to be recorded when
>> a RoutingAppender purge policy attempts to delete an idle appender at
>> exactly the same time as a new event is recorded.
>>         • LOG4J2-2606: Asynchronous logging when the queue is full no
>> longer results in heavy CPU utilization and low throughput.
>> Changes
>>
>>         • : Update tests from H2 1.4.197 to 1.4.199. Thanks to Gary
>> Gregory.
>>         • LOG4J2-2570: Update Jackson from 2.9.7 to 2.9.8. Thanks to Gary
>> Gregory.
>>         • LOG4J2-2574: Update MongoDB 3 module driver from 3.9.0 to
>> 3.10.1. Thanks to Gary Gregory.
>>         • LOG4J2-2619: Update Jackson from 2.9.8 to 2.9.9.
>>         • LOG4J2-2634: Refactor several AsyncLogger methods below the 35
>> byte threshold for inlining.
>>
>> Tag:
>> a)  for a new copy do "git clone
>> https://github.com/apache/logging-log4j2.git" and then "git checkout
>> tags/log4j-2.12.0-rc2”
>> b) for an existing working copy to “git pull” and then “git checkout
>> tags/log4j-2.12.0-rc2”
>>
>> Web Site:  http://rgoers.github.io/log4j2-site/index.html.
>>
>> Maven Artifacts:
>> https://repository.apache.org/content/repositories/orgapachelogging-1047
>>
>> Distribution archives:
>> https://dist.apache.org/repos/dist/dev/logging/log4j/
>>
>> You may download all the Maven artifacts by executing:
>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
>> https://repository.apache.org/content/repositories/orgapachelogging-1047/org/apache/logging/log4j/
>>
>> Ralph
>>
>

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Gary Gregory <ga...@gmail.com>.
FYI, running 'mvn apache-rat:check' fails on log4j-cassandra/.toDelete

Gary

On Tue, Jun 25, 2019 at 11:59 PM Ralph Goers <ra...@dslextreme.com>
wrote:

> This is a vote to release Log4j 2.12.0, the next version of the Log4j 2
> project.
>
> Please download, test, and cast your votes on the log4j developers list.
> [] +1, release the artifacts
> [] -1, don't release because...
>
> The vote will remain open for 72 hours (or more if required). All votes
> are welcome and we encourage everyone to test the release, but only Logging
> PMC votes are “officially” counted. As always, at least 3 +1 votes and more
> positive than negative votes are required.
>
> Changes in this release include:
>
> New Features
>
>         • LOG4J2-2403: Allow zero padding the counter of a
> RollingFileAppender. Thanks to hupfdule.
>         • LOG4J2-2427: Add filter that will match events when no marker is
> present. Thanks to Rimaljit Kaur.
>         • LOG4J2-2406: Add reconfiguration methods to Configurator.
>         • LOG4J2-913: Add support for reconfiguration via HTTP(S), Docker,
> and Spring Cloud Configuration.
>         • LOG4J2-2586: TCP Appender should support a host name resolving
> to multiple IP addresses.
>         • LOG4J2-2337: Allow custom end-of-line with JsonLayout. Thanks to
> Arvind Sahare, Patrice Ferrot.
>         • LOG4J2-2598: GZIP compression on rollover supports configurable
> compression levels. Thanks to Carter Kozak.
>         • LOG4J2-2611: AsyncQueueFullPolicy configuration short values
> "Default" and "Discard" are case insensitive to avoid confusion.
>         • LOG4J2-2634: Add and use method
> org.apache.logging.log4j.message.MapMessage.toKey(String) for simpler
> subclasses.
> Fixed Bugs
>
>         • LOG4J2-2547: RollingRandomAccessFileAppender error message
> referenced incorrect class name.
>         • LOG4J2-2616: Restore constructor to ThrowablePatternConverter
> that was removed in 2.8.2.
>         • LOG4J2-2622: StructuredDataId was ignoring maxLength atribute.
>         • LOG4J2-2636: RFC5424Layout was not properly setting default
> Structured Element id for the MDC
>         • LOG4J2-1143: Lookups were not found if the plugin key was not
> lowercase. Thanks to Pascal Heinrich.
>         • LOG4J2-1852: Locate plugins within a Jar using a URL Connection.
> Thanks to Tanner Altares.
>         • LOG4J2-2610: Explicitly set file creation time.
>         • LOG4J2-2561: JEP223 version detection fix for JDK 9 and up.
> Thanks to Ulrich Enslin.
>         • LOG4J2-1103: FailoverAppender was failing with ERROR appender
> Failover has no parameter that matches element Failovers. Thanks to Seán
> Dunne.
>         • LOG4J2-2602: Update file time when size based triggering policy
> is used without a time-based triggering policy.
>         • LOG4J2-2597: Throw better exception message when both
> log4j-slf4j-impl and log4j-to-slf4j are present.
>         • LOG4J2-2559: NullPointerException in
> JdbcAppender.createAppender(). Thanks to Li Lei, Gary Gregory.
>         • LOG4J2-2592: StackOverflowException when server not reachable
> with SocketAppender. Thanks to Dávid Kaya, Gary Gregory.
>         • LOG4J2-2598: java.lang.StackOverflowError at
> org.apache.logging.log4j.junit.AbstractExternalFileCleaner.println(AbstractExternalFileCleaner.java:169).
> Thanks to Gary Gregory.
>         • LOG4J2-2564: MapPatternConverter is properly created from the
> '%K', '%map', and '%MAP' patterns. PatternConverter instanceOf methods with
> unknown parameter types no longer elide those with known parameters.
>         • LOG4J2-2612: NullPointerException at
> org.apache.logging.log4j.core.appender.db.jdbc.JdbcDatabaseManager.writeInternal(JdbcDatabaseManager.java:803).
>         • LOG4J2-2618: Possible ClassCastException in
> org.apache.logging.log4j.core.script.ScriptManager.ScriptManager(Configuration,
> WatchManager)
>         • LOG4J2-2631: RoutingAppender PurgePolicy implementations no
> longer stop appenders referenced from the logger configuration, only those
> that have been created by the RoutingAppender. Note that
> RoutingAppender.getAppenders no longer includes entries for referenced
> appenders, only those which it has created.
>         • LOG4J2-2629: Fix a race allowing events not to be recorded when
> a RoutingAppender purge policy attempts to delete an idle appender at
> exactly the same time as a new event is recorded.
>         • LOG4J2-2606: Asynchronous logging when the queue is full no
> longer results in heavy CPU utilization and low throughput.
> Changes
>
>         • : Update tests from H2 1.4.197 to 1.4.199. Thanks to Gary
> Gregory.
>         • LOG4J2-2570: Update Jackson from 2.9.7 to 2.9.8. Thanks to Gary
> Gregory.
>         • LOG4J2-2574: Update MongoDB 3 module driver from 3.9.0 to
> 3.10.1. Thanks to Gary Gregory.
>         • LOG4J2-2619: Update Jackson from 2.9.8 to 2.9.9.
>         • LOG4J2-2634: Refactor several AsyncLogger methods below the 35
> byte threshold for inlining.
>
> Tag:
> a)  for a new copy do "git clone
> https://github.com/apache/logging-log4j2.git" and then "git checkout
> tags/log4j-2.12.0-rc2”
> b) for an existing working copy to “git pull” and then “git checkout
> tags/log4j-2.12.0-rc2”
>
> Web Site:  http://rgoers.github.io/log4j2-site/index.html.
>
> Maven Artifacts:
> https://repository.apache.org/content/repositories/orgapachelogging-1047
>
> Distribution archives:
> https://dist.apache.org/repos/dist/dev/logging/log4j/
>
> You may download all the Maven artifacts by executing:
> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
> https://repository.apache.org/content/repositories/orgapachelogging-1047/org/apache/logging/log4j/
>
> Ralph
>

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Ralph Goers <ra...@dslextreme.com>.
I have fixed the module so that the rat plugin now runs. It had one file with a license problem - a log4j2.xml used by the sample server. Although the sample server is included in the source release it is not deployed to Nexus. Since it is just a sample I don’t feel it warrants spinning a new release.

Ralph

> On Jun 26, 2019, at 1:12 PM, Ralph Goers <ra...@dslextreme.com> wrote:
> 
> Nevermind. I see you used reflection. I am not sure why I hadn’t thought of doing that. 
> 
> Ralph
> 
>> On Jun 26, 2019, at 1:08 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>> 
>> How did you get around the compile problem in master?
>> 
>> Ralph
>> 
>>> On Jun 26, 2019, at 12:36 PM, Matt Sicker <bo...@gmail.com> wrote:
>>> 
>>> I fixed that sun.reflect compile error in master, but didn't backport
>>> it to release-2.x. There are still some other compile errors besides
>>> if you compile with Java 11.
>>> 
>>> As for why you get different results when running rat with or without
>>> the rat profile activated, it's because our rat config is different in
>>> the rat profile compared to the default one. I think our config is
>>> wrong there, and I typically rediscover that any time I do a release.
>>> 
>>> On Wed, 26 Jun 2019 at 13:15, Ralph Goers <ra...@dslextreme.com> wrote:
>>>> 
>>>> I have wondered that for a long time. In fact, if you run “mvn compile” followed by “mvn test” you will see
>>>> 
>>>> [INFO] Changes detected - recompiling the module!
>>>> 
>>>> So obviously something is there that tries to detect changes. It just doesn’t seem to work.
>>>> 
>>>> Ralph
>>>> 
>>>> 
>>>> 
>>>> 
>>>>> On Jun 26, 2019, at 9:32 AM, Gary Gregory <ga...@gmail.com> wrote:
>>>>> 
>>>>> On Wed, Jun 26, 2019 at 12:24 PM Ralph Goers <ra...@dslextreme.com>
>>>>> wrote:
>>>>> 
>>>>>> Those are mine as well.
>>>>>> 
>>>>>> Unfortunately, if you use the toolchains plugin to specify the compiler
>>>>>> version then all the tests are also going to run with that Java version.
>>>>>> Since there is no getting around having sun.reflect.Reflection be used
>>>>>> prior to Java 9 there is no way to use Java 11 to compile and test Log4j
>>>>>> API.  That only leaves you with the option of creating a phony jar. But
>>>>>> that will have problems too as it will probably be used by the unit tests.
>>>>>> 
>>>>>> The only other option is to create a separate module for the unit tests.
>>>>>> 
>>>>> 
>>>>> But why does Maven recompile when nothing has changed? That's the real
>>>>> problem, I ran a first build on Java 8, then all I want to do is run the
>>>>> tests on Java 11.
>>>>> 
>>>>> Gary
>>>>> 
>>>>>> 
>>>>>> Ralph
>>>>>> 
>>>>>>> On Jun 26, 2019, at 9:00 AM, Gary Gregory <ga...@gmail.com>
>>>>>> wrote:
>>>>>>> 
>>>>>>> On Wed, Jun 26, 2019 at 11:02 AM Ralph Goers <ralph.goers@dslextreme.com
>>>>>>> 
>>>>>>> wrote:
>>>>>>> 
>>>>>>>> I don’t run the build with Java 11, although I do have projects that use
>>>>>>>> it that are on Java 11. It seems that log4j-api is failing when
>>>>>> compiling
>>>>>>>> with Java 11 because sun.reflect.Reflection was removed in Java 9.  I
>>>>>> guess
>>>>>>>> we need to modify the toolchains configuration to tell the main modules
>>>>>> to
>>>>>>>> use only Java 8 to compile.  The only other option would be to create a
>>>>>> jar
>>>>>>>> that has that class in it and specify it as a provided dependency.
>>>>>>>> 
>>>>>>> 
>>>>>>> My goal is to be able to answer the question: "Do all the tests pass on
>>>>>>> Java 11?"
>>>>>>> 
>>>>>>> I am OK for this release with not being able to _build_ on Java 11 but I
>>>>>>> certainly should be able to run all tests with a plain old 'mvn test'.
>>>>>>> 
>>>>>>> FWIW, at work, our platform requirements are Java 8 and 11.
>>>>>>> 
>>>>>>> Gary
>>>>>> 
>>>>>> 
>>>> 
>>>> 
>>> 
>>> 
>>> -- 
>>> Matt Sicker <bo...@gmail.com>
>>> 
>> 
>> 
>> 
> 
> 
>

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Matt Sicker <bo...@gmail.com>.
I made it a JUnit assume so it would ignore the test when the class
isn't found. I think I made a Hamcrest matcher for it.

On Wed, 26 Jun 2019 at 23:04, Ralph Goers <ra...@dslextreme.com> wrote:
>
> I tried porting the changes you made back to release-2.x and it compiles, but it still fails in the unit tests as the reflection fails since the class isn’t present. How did you solve that?
>
> Ralph
>
> > On Jun 26, 2019, at 1:12 PM, Ralph Goers <ra...@dslextreme.com> wrote:
> >
> > Nevermind. I see you used reflection. I am not sure why I hadn’t thought of doing that.
> >
> > Ralph
> >
> >> On Jun 26, 2019, at 1:08 PM, Ralph Goers <ra...@dslextreme.com> wrote:
> >>
> >> How did you get around the compile problem in master?
> >>
> >> Ralph
> >>
> >>> On Jun 26, 2019, at 12:36 PM, Matt Sicker <bo...@gmail.com> wrote:
> >>>
> >>> I fixed that sun.reflect compile error in master, but didn't backport
> >>> it to release-2.x. There are still some other compile errors besides
> >>> if you compile with Java 11.
> >>>
> >>> As for why you get different results when running rat with or without
> >>> the rat profile activated, it's because our rat config is different in
> >>> the rat profile compared to the default one. I think our config is
> >>> wrong there, and I typically rediscover that any time I do a release.
> >>>
> >>> On Wed, 26 Jun 2019 at 13:15, Ralph Goers <ra...@dslextreme.com> wrote:
> >>>>
> >>>> I have wondered that for a long time. In fact, if you run “mvn compile” followed by “mvn test” you will see
> >>>>
> >>>> [INFO] Changes detected - recompiling the module!
> >>>>
> >>>> So obviously something is there that tries to detect changes. It just doesn’t seem to work.
> >>>>
> >>>> Ralph
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> On Jun 26, 2019, at 9:32 AM, Gary Gregory <ga...@gmail.com> wrote:
> >>>>>
> >>>>> On Wed, Jun 26, 2019 at 12:24 PM Ralph Goers <ra...@dslextreme.com>
> >>>>> wrote:
> >>>>>
> >>>>>> Those are mine as well.
> >>>>>>
> >>>>>> Unfortunately, if you use the toolchains plugin to specify the compiler
> >>>>>> version then all the tests are also going to run with that Java version.
> >>>>>> Since there is no getting around having sun.reflect.Reflection be used
> >>>>>> prior to Java 9 there is no way to use Java 11 to compile and test Log4j
> >>>>>> API.  That only leaves you with the option of creating a phony jar. But
> >>>>>> that will have problems too as it will probably be used by the unit tests.
> >>>>>>
> >>>>>> The only other option is to create a separate module for the unit tests.
> >>>>>>
> >>>>>
> >>>>> But why does Maven recompile when nothing has changed? That's the real
> >>>>> problem, I ran a first build on Java 8, then all I want to do is run the
> >>>>> tests on Java 11.
> >>>>>
> >>>>> Gary
> >>>>>
> >>>>>>
> >>>>>> Ralph
> >>>>>>
> >>>>>>> On Jun 26, 2019, at 9:00 AM, Gary Gregory <ga...@gmail.com>
> >>>>>> wrote:
> >>>>>>>
> >>>>>>> On Wed, Jun 26, 2019 at 11:02 AM Ralph Goers <ralph.goers@dslextreme.com
> >>>>>>>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> I don’t run the build with Java 11, although I do have projects that use
> >>>>>>>> it that are on Java 11. It seems that log4j-api is failing when
> >>>>>> compiling
> >>>>>>>> with Java 11 because sun.reflect.Reflection was removed in Java 9.  I
> >>>>>> guess
> >>>>>>>> we need to modify the toolchains configuration to tell the main modules
> >>>>>> to
> >>>>>>>> use only Java 8 to compile.  The only other option would be to create a
> >>>>>> jar
> >>>>>>>> that has that class in it and specify it as a provided dependency.
> >>>>>>>>
> >>>>>>>
> >>>>>>> My goal is to be able to answer the question: "Do all the tests pass on
> >>>>>>> Java 11?"
> >>>>>>>
> >>>>>>> I am OK for this release with not being able to _build_ on Java 11 but I
> >>>>>>> certainly should be able to run all tests with a plain old 'mvn test'.
> >>>>>>>
> >>>>>>> FWIW, at work, our platform requirements are Java 8 and 11.
> >>>>>>>
> >>>>>>> Gary
> >>>>>>
> >>>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Matt Sicker <bo...@gmail.com>
> >>>
> >>
> >>
> >>
> >
> >
> >
>
>


-- 
Matt Sicker <bo...@gmail.com>

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Ralph Goers <ra...@dslextreme.com>.
I tried porting the changes you made back to release-2.x and it compiles, but it still fails in the unit tests as the reflection fails since the class isn’t present. How did you solve that?

Ralph

> On Jun 26, 2019, at 1:12 PM, Ralph Goers <ra...@dslextreme.com> wrote:
> 
> Nevermind. I see you used reflection. I am not sure why I hadn’t thought of doing that. 
> 
> Ralph
> 
>> On Jun 26, 2019, at 1:08 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>> 
>> How did you get around the compile problem in master?
>> 
>> Ralph
>> 
>>> On Jun 26, 2019, at 12:36 PM, Matt Sicker <bo...@gmail.com> wrote:
>>> 
>>> I fixed that sun.reflect compile error in master, but didn't backport
>>> it to release-2.x. There are still some other compile errors besides
>>> if you compile with Java 11.
>>> 
>>> As for why you get different results when running rat with or without
>>> the rat profile activated, it's because our rat config is different in
>>> the rat profile compared to the default one. I think our config is
>>> wrong there, and I typically rediscover that any time I do a release.
>>> 
>>> On Wed, 26 Jun 2019 at 13:15, Ralph Goers <ra...@dslextreme.com> wrote:
>>>> 
>>>> I have wondered that for a long time. In fact, if you run “mvn compile” followed by “mvn test” you will see
>>>> 
>>>> [INFO] Changes detected - recompiling the module!
>>>> 
>>>> So obviously something is there that tries to detect changes. It just doesn’t seem to work.
>>>> 
>>>> Ralph
>>>> 
>>>> 
>>>> 
>>>> 
>>>>> On Jun 26, 2019, at 9:32 AM, Gary Gregory <ga...@gmail.com> wrote:
>>>>> 
>>>>> On Wed, Jun 26, 2019 at 12:24 PM Ralph Goers <ra...@dslextreme.com>
>>>>> wrote:
>>>>> 
>>>>>> Those are mine as well.
>>>>>> 
>>>>>> Unfortunately, if you use the toolchains plugin to specify the compiler
>>>>>> version then all the tests are also going to run with that Java version.
>>>>>> Since there is no getting around having sun.reflect.Reflection be used
>>>>>> prior to Java 9 there is no way to use Java 11 to compile and test Log4j
>>>>>> API.  That only leaves you with the option of creating a phony jar. But
>>>>>> that will have problems too as it will probably be used by the unit tests.
>>>>>> 
>>>>>> The only other option is to create a separate module for the unit tests.
>>>>>> 
>>>>> 
>>>>> But why does Maven recompile when nothing has changed? That's the real
>>>>> problem, I ran a first build on Java 8, then all I want to do is run the
>>>>> tests on Java 11.
>>>>> 
>>>>> Gary
>>>>> 
>>>>>> 
>>>>>> Ralph
>>>>>> 
>>>>>>> On Jun 26, 2019, at 9:00 AM, Gary Gregory <ga...@gmail.com>
>>>>>> wrote:
>>>>>>> 
>>>>>>> On Wed, Jun 26, 2019 at 11:02 AM Ralph Goers <ralph.goers@dslextreme.com
>>>>>>> 
>>>>>>> wrote:
>>>>>>> 
>>>>>>>> I don’t run the build with Java 11, although I do have projects that use
>>>>>>>> it that are on Java 11. It seems that log4j-api is failing when
>>>>>> compiling
>>>>>>>> with Java 11 because sun.reflect.Reflection was removed in Java 9.  I
>>>>>> guess
>>>>>>>> we need to modify the toolchains configuration to tell the main modules
>>>>>> to
>>>>>>>> use only Java 8 to compile.  The only other option would be to create a
>>>>>> jar
>>>>>>>> that has that class in it and specify it as a provided dependency.
>>>>>>>> 
>>>>>>> 
>>>>>>> My goal is to be able to answer the question: "Do all the tests pass on
>>>>>>> Java 11?"
>>>>>>> 
>>>>>>> I am OK for this release with not being able to _build_ on Java 11 but I
>>>>>>> certainly should be able to run all tests with a plain old 'mvn test'.
>>>>>>> 
>>>>>>> FWIW, at work, our platform requirements are Java 8 and 11.
>>>>>>> 
>>>>>>> Gary
>>>>>> 
>>>>>> 
>>>> 
>>>> 
>>> 
>>> 
>>> -- 
>>> Matt Sicker <bo...@gmail.com>
>>> 
>> 
>> 
>> 
> 
> 
>

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Ralph Goers <ra...@dslextreme.com>.
Nevermind. I see you used reflection. I am not sure why I hadn’t thought of doing that. 

Ralph

> On Jun 26, 2019, at 1:08 PM, Ralph Goers <ra...@dslextreme.com> wrote:
> 
> How did you get around the compile problem in master?
> 
> Ralph
> 
>> On Jun 26, 2019, at 12:36 PM, Matt Sicker <bo...@gmail.com> wrote:
>> 
>> I fixed that sun.reflect compile error in master, but didn't backport
>> it to release-2.x. There are still some other compile errors besides
>> if you compile with Java 11.
>> 
>> As for why you get different results when running rat with or without
>> the rat profile activated, it's because our rat config is different in
>> the rat profile compared to the default one. I think our config is
>> wrong there, and I typically rediscover that any time I do a release.
>> 
>> On Wed, 26 Jun 2019 at 13:15, Ralph Goers <ra...@dslextreme.com> wrote:
>>> 
>>> I have wondered that for a long time. In fact, if you run “mvn compile” followed by “mvn test” you will see
>>> 
>>> [INFO] Changes detected - recompiling the module!
>>> 
>>> So obviously something is there that tries to detect changes. It just doesn’t seem to work.
>>> 
>>> Ralph
>>> 
>>> 
>>> 
>>> 
>>>> On Jun 26, 2019, at 9:32 AM, Gary Gregory <ga...@gmail.com> wrote:
>>>> 
>>>> On Wed, Jun 26, 2019 at 12:24 PM Ralph Goers <ra...@dslextreme.com>
>>>> wrote:
>>>> 
>>>>> Those are mine as well.
>>>>> 
>>>>> Unfortunately, if you use the toolchains plugin to specify the compiler
>>>>> version then all the tests are also going to run with that Java version.
>>>>> Since there is no getting around having sun.reflect.Reflection be used
>>>>> prior to Java 9 there is no way to use Java 11 to compile and test Log4j
>>>>> API.  That only leaves you with the option of creating a phony jar. But
>>>>> that will have problems too as it will probably be used by the unit tests.
>>>>> 
>>>>> The only other option is to create a separate module for the unit tests.
>>>>> 
>>>> 
>>>> But why does Maven recompile when nothing has changed? That's the real
>>>> problem, I ran a first build on Java 8, then all I want to do is run the
>>>> tests on Java 11.
>>>> 
>>>> Gary
>>>> 
>>>>> 
>>>>> Ralph
>>>>> 
>>>>>> On Jun 26, 2019, at 9:00 AM, Gary Gregory <ga...@gmail.com>
>>>>> wrote:
>>>>>> 
>>>>>> On Wed, Jun 26, 2019 at 11:02 AM Ralph Goers <ralph.goers@dslextreme.com
>>>>>> 
>>>>>> wrote:
>>>>>> 
>>>>>>> I don’t run the build with Java 11, although I do have projects that use
>>>>>>> it that are on Java 11. It seems that log4j-api is failing when
>>>>> compiling
>>>>>>> with Java 11 because sun.reflect.Reflection was removed in Java 9.  I
>>>>> guess
>>>>>>> we need to modify the toolchains configuration to tell the main modules
>>>>> to
>>>>>>> use only Java 8 to compile.  The only other option would be to create a
>>>>> jar
>>>>>>> that has that class in it and specify it as a provided dependency.
>>>>>>> 
>>>>>> 
>>>>>> My goal is to be able to answer the question: "Do all the tests pass on
>>>>>> Java 11?"
>>>>>> 
>>>>>> I am OK for this release with not being able to _build_ on Java 11 but I
>>>>>> certainly should be able to run all tests with a plain old 'mvn test'.
>>>>>> 
>>>>>> FWIW, at work, our platform requirements are Java 8 and 11.
>>>>>> 
>>>>>> Gary
>>>>> 
>>>>> 
>>> 
>>> 
>> 
>> 
>> -- 
>> Matt Sicker <bo...@gmail.com>
>> 
> 
> 
>

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Ralph Goers <ra...@dslextreme.com>.
How did you get around the compile problem in master?

Ralph

> On Jun 26, 2019, at 12:36 PM, Matt Sicker <bo...@gmail.com> wrote:
> 
> I fixed that sun.reflect compile error in master, but didn't backport
> it to release-2.x. There are still some other compile errors besides
> if you compile with Java 11.
> 
> As for why you get different results when running rat with or without
> the rat profile activated, it's because our rat config is different in
> the rat profile compared to the default one. I think our config is
> wrong there, and I typically rediscover that any time I do a release.
> 
> On Wed, 26 Jun 2019 at 13:15, Ralph Goers <ra...@dslextreme.com> wrote:
>> 
>> I have wondered that for a long time. In fact, if you run “mvn compile” followed by “mvn test” you will see
>> 
>> [INFO] Changes detected - recompiling the module!
>> 
>> So obviously something is there that tries to detect changes. It just doesn’t seem to work.
>> 
>> Ralph
>> 
>> 
>> 
>> 
>>> On Jun 26, 2019, at 9:32 AM, Gary Gregory <ga...@gmail.com> wrote:
>>> 
>>> On Wed, Jun 26, 2019 at 12:24 PM Ralph Goers <ra...@dslextreme.com>
>>> wrote:
>>> 
>>>> Those are mine as well.
>>>> 
>>>> Unfortunately, if you use the toolchains plugin to specify the compiler
>>>> version then all the tests are also going to run with that Java version.
>>>> Since there is no getting around having sun.reflect.Reflection be used
>>>> prior to Java 9 there is no way to use Java 11 to compile and test Log4j
>>>> API.  That only leaves you with the option of creating a phony jar. But
>>>> that will have problems too as it will probably be used by the unit tests.
>>>> 
>>>> The only other option is to create a separate module for the unit tests.
>>>> 
>>> 
>>> But why does Maven recompile when nothing has changed? That's the real
>>> problem, I ran a first build on Java 8, then all I want to do is run the
>>> tests on Java 11.
>>> 
>>> Gary
>>> 
>>>> 
>>>> Ralph
>>>> 
>>>>> On Jun 26, 2019, at 9:00 AM, Gary Gregory <ga...@gmail.com>
>>>> wrote:
>>>>> 
>>>>> On Wed, Jun 26, 2019 at 11:02 AM Ralph Goers <ralph.goers@dslextreme.com
>>>>> 
>>>>> wrote:
>>>>> 
>>>>>> I don’t run the build with Java 11, although I do have projects that use
>>>>>> it that are on Java 11. It seems that log4j-api is failing when
>>>> compiling
>>>>>> with Java 11 because sun.reflect.Reflection was removed in Java 9.  I
>>>> guess
>>>>>> we need to modify the toolchains configuration to tell the main modules
>>>> to
>>>>>> use only Java 8 to compile.  The only other option would be to create a
>>>> jar
>>>>>> that has that class in it and specify it as a provided dependency.
>>>>>> 
>>>>> 
>>>>> My goal is to be able to answer the question: "Do all the tests pass on
>>>>> Java 11?"
>>>>> 
>>>>> I am OK for this release with not being able to _build_ on Java 11 but I
>>>>> certainly should be able to run all tests with a plain old 'mvn test'.
>>>>> 
>>>>> FWIW, at work, our platform requirements are Java 8 and 11.
>>>>> 
>>>>> Gary
>>>> 
>>>> 
>> 
>> 
> 
> 
> -- 
> Matt Sicker <bo...@gmail.com>
>

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Matt Sicker <bo...@gmail.com>.
I fixed that sun.reflect compile error in master, but didn't backport
it to release-2.x. There are still some other compile errors besides
if you compile with Java 11.

As for why you get different results when running rat with or without
the rat profile activated, it's because our rat config is different in
the rat profile compared to the default one. I think our config is
wrong there, and I typically rediscover that any time I do a release.

On Wed, 26 Jun 2019 at 13:15, Ralph Goers <ra...@dslextreme.com> wrote:
>
> I have wondered that for a long time. In fact, if you run “mvn compile” followed by “mvn test” you will see
>
> [INFO] Changes detected - recompiling the module!
>
> So obviously something is there that tries to detect changes. It just doesn’t seem to work.
>
> Ralph
>
>
>
>
> > On Jun 26, 2019, at 9:32 AM, Gary Gregory <ga...@gmail.com> wrote:
> >
> > On Wed, Jun 26, 2019 at 12:24 PM Ralph Goers <ra...@dslextreme.com>
> > wrote:
> >
> >> Those are mine as well.
> >>
> >> Unfortunately, if you use the toolchains plugin to specify the compiler
> >> version then all the tests are also going to run with that Java version.
> >> Since there is no getting around having sun.reflect.Reflection be used
> >> prior to Java 9 there is no way to use Java 11 to compile and test Log4j
> >> API.  That only leaves you with the option of creating a phony jar. But
> >> that will have problems too as it will probably be used by the unit tests.
> >>
> >> The only other option is to create a separate module for the unit tests.
> >>
> >
> > But why does Maven recompile when nothing has changed? That's the real
> > problem, I ran a first build on Java 8, then all I want to do is run the
> > tests on Java 11.
> >
> > Gary
> >
> >>
> >> Ralph
> >>
> >>> On Jun 26, 2019, at 9:00 AM, Gary Gregory <ga...@gmail.com>
> >> wrote:
> >>>
> >>> On Wed, Jun 26, 2019 at 11:02 AM Ralph Goers <ralph.goers@dslextreme.com
> >>>
> >>> wrote:
> >>>
> >>>> I don’t run the build with Java 11, although I do have projects that use
> >>>> it that are on Java 11. It seems that log4j-api is failing when
> >> compiling
> >>>> with Java 11 because sun.reflect.Reflection was removed in Java 9.  I
> >> guess
> >>>> we need to modify the toolchains configuration to tell the main modules
> >> to
> >>>> use only Java 8 to compile.  The only other option would be to create a
> >> jar
> >>>> that has that class in it and specify it as a provided dependency.
> >>>>
> >>>
> >>> My goal is to be able to answer the question: "Do all the tests pass on
> >>> Java 11?"
> >>>
> >>> I am OK for this release with not being able to _build_ on Java 11 but I
> >>> certainly should be able to run all tests with a plain old 'mvn test'.
> >>>
> >>> FWIW, at work, our platform requirements are Java 8 and 11.
> >>>
> >>> Gary
> >>
> >>
>
>


-- 
Matt Sicker <bo...@gmail.com>

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Ralph Goers <ra...@dslextreme.com>.
I have wondered that for a long time. In fact, if you run “mvn compile” followed by “mvn test” you will see

[INFO] Changes detected - recompiling the module!

So obviously something is there that tries to detect changes. It just doesn’t seem to work.

Ralph




> On Jun 26, 2019, at 9:32 AM, Gary Gregory <ga...@gmail.com> wrote:
> 
> On Wed, Jun 26, 2019 at 12:24 PM Ralph Goers <ra...@dslextreme.com>
> wrote:
> 
>> Those are mine as well.
>> 
>> Unfortunately, if you use the toolchains plugin to specify the compiler
>> version then all the tests are also going to run with that Java version.
>> Since there is no getting around having sun.reflect.Reflection be used
>> prior to Java 9 there is no way to use Java 11 to compile and test Log4j
>> API.  That only leaves you with the option of creating a phony jar. But
>> that will have problems too as it will probably be used by the unit tests.
>> 
>> The only other option is to create a separate module for the unit tests.
>> 
> 
> But why does Maven recompile when nothing has changed? That's the real
> problem, I ran a first build on Java 8, then all I want to do is run the
> tests on Java 11.
> 
> Gary
> 
>> 
>> Ralph
>> 
>>> On Jun 26, 2019, at 9:00 AM, Gary Gregory <ga...@gmail.com>
>> wrote:
>>> 
>>> On Wed, Jun 26, 2019 at 11:02 AM Ralph Goers <ralph.goers@dslextreme.com
>>> 
>>> wrote:
>>> 
>>>> I don’t run the build with Java 11, although I do have projects that use
>>>> it that are on Java 11. It seems that log4j-api is failing when
>> compiling
>>>> with Java 11 because sun.reflect.Reflection was removed in Java 9.  I
>> guess
>>>> we need to modify the toolchains configuration to tell the main modules
>> to
>>>> use only Java 8 to compile.  The only other option would be to create a
>> jar
>>>> that has that class in it and specify it as a provided dependency.
>>>> 
>>> 
>>> My goal is to be able to answer the question: "Do all the tests pass on
>>> Java 11?"
>>> 
>>> I am OK for this release with not being able to _build_ on Java 11 but I
>>> certainly should be able to run all tests with a plain old 'mvn test'.
>>> 
>>> FWIW, at work, our platform requirements are Java 8 and 11.
>>> 
>>> Gary
>> 
>>

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Gary Gregory <ga...@gmail.com>.
On Wed, Jun 26, 2019 at 12:24 PM Ralph Goers <ra...@dslextreme.com>
wrote:

> Those are mine as well.
>
> Unfortunately, if you use the toolchains plugin to specify the compiler
> version then all the tests are also going to run with that Java version.
> Since there is no getting around having sun.reflect.Reflection be used
> prior to Java 9 there is no way to use Java 11 to compile and test Log4j
> API.  That only leaves you with the option of creating a phony jar. But
> that will have problems too as it will probably be used by the unit tests.
>
> The only other option is to create a separate module for the unit tests.
>

But why does Maven recompile when nothing has changed? That's the real
problem, I ran a first build on Java 8, then all I want to do is run the
tests on Java 11.

Gary

>
> Ralph
>
> > On Jun 26, 2019, at 9:00 AM, Gary Gregory <ga...@gmail.com>
> wrote:
> >
> > On Wed, Jun 26, 2019 at 11:02 AM Ralph Goers <ralph.goers@dslextreme.com
> >
> > wrote:
> >
> >> I don’t run the build with Java 11, although I do have projects that use
> >> it that are on Java 11. It seems that log4j-api is failing when
> compiling
> >> with Java 11 because sun.reflect.Reflection was removed in Java 9.  I
> guess
> >> we need to modify the toolchains configuration to tell the main modules
> to
> >> use only Java 8 to compile.  The only other option would be to create a
> jar
> >> that has that class in it and specify it as a provided dependency.
> >>
> >
> > My goal is to be able to answer the question: "Do all the tests pass on
> > Java 11?"
> >
> > I am OK for this release with not being able to _build_ on Java 11 but I
> > certainly should be able to run all tests with a plain old 'mvn test'.
> >
> > FWIW, at work, our platform requirements are Java 8 and 11.
> >
> > Gary
>
>

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Ralph Goers <ra...@dslextreme.com>.
Those are mine as well. 

Unfortunately, if you use the toolchains plugin to specify the compiler version then all the tests are also going to run with that Java version. Since there is no getting around having sun.reflect.Reflection be used prior to Java 9 there is no way to use Java 11 to compile and test Log4j API.  That only leaves you with the option of creating a phony jar. But that will have problems too as it will probably be used by the unit tests.

The only other option is to create a separate module for the unit tests.

Ralph

> On Jun 26, 2019, at 9:00 AM, Gary Gregory <ga...@gmail.com> wrote:
> 
> On Wed, Jun 26, 2019 at 11:02 AM Ralph Goers <ra...@dslextreme.com>
> wrote:
> 
>> I don’t run the build with Java 11, although I do have projects that use
>> it that are on Java 11. It seems that log4j-api is failing when compiling
>> with Java 11 because sun.reflect.Reflection was removed in Java 9.  I guess
>> we need to modify the toolchains configuration to tell the main modules to
>> use only Java 8 to compile.  The only other option would be to create a jar
>> that has that class in it and specify it as a provided dependency.
>> 
> 
> My goal is to be able to answer the question: "Do all the tests pass on
> Java 11?"
> 
> I am OK for this release with not being able to _build_ on Java 11 but I
> certainly should be able to run all tests with a plain old 'mvn test'.
> 
> FWIW, at work, our platform requirements are Java 8 and 11.
> 
> Gary

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Gary Gregory <ga...@gmail.com>.
On Wed, Jun 26, 2019 at 11:02 AM Ralph Goers <ra...@dslextreme.com>
wrote:

> I don’t run the build with Java 11, although I do have projects that use
> it that are on Java 11. It seems that log4j-api is failing when compiling
> with Java 11 because sun.reflect.Reflection was removed in Java 9.  I guess
> we need to modify the toolchains configuration to tell the main modules to
> use only Java 8 to compile.  The only other option would be to create a jar
> that has that class in it and specify it as a provided dependency.
>

My goal is to be able to answer the question: "Do all the tests pass on
Java 11?"

I am OK for this release with not being able to _build_ on Java 11 but I
certainly should be able to run all tests with a plain old 'mvn test'.

FWIW, at work, our platform requirements are Java 8 and 11.

Gary


> Ralph
>
> > On Jun 26, 2019, at 7:32 AM, Gary Gregory <ga...@gmail.com>
> wrote:
> >
> > Driving me nuts: I can do the following OK on Java 8: " mvn -P rat
> > -DskipTests clean install".
> > But then I switch to Java 11 and run "mvn test" and Maven wants to
> > recompile everything and fails as noted below.
> > How do you test on Java 11?
> >
> > Gary
> >
> > On Wed, Jun 26, 2019 at 10:24 AM Gary Gregory <ga...@gmail.com>
> > wrote:
> >
> >> Note: Compiling on Java 11 fails:
> >>
> >> [INFO] --- maven-compiler-plugin:3.8.1:testCompile
> (default-testCompile) @
> >> log4j-api ---
> >> [INFO] Changes detected - recompiling the module!
> >> [INFO] Compiling 84 source files to
> >> C:\temp\rc\logging-log4j2\log4j-api\target\test-classes
> >> [INFO] -------------------------------------------------------------
> >> [WARNING] COMPILATION WARNING :
> >> [INFO] -------------------------------------------------------------
> >> [WARNING] [options] bootstrap class path not set in conjunction with
> >> -source 7
> >> [WARNING] No processor claimed any of these annotations:
> >>
> org.junit.AfterClass,org.junit.Rule,org.junit.BeforeClass,org.junit.Ignore,org.junit.After,org.junit.runner.RunWith,org.junit.runners.Parameterized.Parameters,org.junit.Test,org.junit.ClassRule,org.junit.Before
> >> [INFO] 2 warnings
> >> [INFO] -------------------------------------------------------------
> >> [INFO] -------------------------------------------------------------
> >> [ERROR] COMPILATION ERROR :
> >> [INFO] -------------------------------------------------------------
> >> [ERROR]
> >>
> C:\temp\rc\logging-log4j2\log4j-api\src\test\java\org\apache\logging\log4j\util\StackLocatorUtilTest.java:[25,18]
> >> error: cannot find symbol
> >>  symbol:   class Reflection
> >>  location: package sun.reflect
> >> [INFO] 1 error
> >> [INFO] -------------------------------------------------------------
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] Reactor Summary for Apache Log4j 2 2.12.0:
> >> [INFO]
> >> [INFO] Apache Log4j 2 ..................................... SUCCESS [
> >> 3.167 s]
> >> [INFO] Apache Log4j API Java 9 support .................... SUCCESS [
> >> 6.356 s]
> >> [INFO] Apache Log4j API ................................... FAILURE [
> >> 10.530 s]
> >>
> >> Gary
> >>
> >>
> >> On Tue, Jun 25, 2019 at 11:59 PM Ralph Goers <
> ralph.goers@dslextreme.com>
> >> wrote:
> >>
> >>> This is a vote to release Log4j 2.12.0, the next version of the Log4j 2
> >>> project.
> >>>
> >>> Please download, test, and cast your votes on the log4j developers
> list.
> >>> [] +1, release the artifacts
> >>> [] -1, don't release because...
> >>>
> >>> The vote will remain open for 72 hours (or more if required). All votes
> >>> are welcome and we encourage everyone to test the release, but only
> Logging
> >>> PMC votes are “officially” counted. As always, at least 3 +1 votes and
> more
> >>> positive than negative votes are required.
> >>>
> >>> Changes in this release include:
> >>>
> >>> New Features
> >>>
> >>>        • LOG4J2-2403: Allow zero padding the counter of a
> >>> RollingFileAppender. Thanks to hupfdule.
> >>>        • LOG4J2-2427: Add filter that will match events when no marker
> >>> is present. Thanks to Rimaljit Kaur.
> >>>        • LOG4J2-2406: Add reconfiguration methods to Configurator.
> >>>        • LOG4J2-913: Add support for reconfiguration via HTTP(S),
> >>> Docker, and Spring Cloud Configuration.
> >>>        • LOG4J2-2586: TCP Appender should support a host name resolving
> >>> to multiple IP addresses.
> >>>        • LOG4J2-2337: Allow custom end-of-line with JsonLayout. Thanks
> >>> to Arvind Sahare, Patrice Ferrot.
> >>>        • LOG4J2-2598: GZIP compression on rollover supports
> configurable
> >>> compression levels. Thanks to Carter Kozak.
> >>>        • LOG4J2-2611: AsyncQueueFullPolicy configuration short values
> >>> "Default" and "Discard" are case insensitive to avoid confusion.
> >>>        • LOG4J2-2634: Add and use method
> >>> org.apache.logging.log4j.message.MapMessage.toKey(String) for simpler
> >>> subclasses.
> >>> Fixed Bugs
> >>>
> >>>        • LOG4J2-2547: RollingRandomAccessFileAppender error message
> >>> referenced incorrect class name.
> >>>        • LOG4J2-2616: Restore constructor to ThrowablePatternConverter
> >>> that was removed in 2.8.2.
> >>>        • LOG4J2-2622: StructuredDataId was ignoring maxLength atribute.
> >>>        • LOG4J2-2636: RFC5424Layout was not properly setting default
> >>> Structured Element id for the MDC
> >>>        • LOG4J2-1143: Lookups were not found if the plugin key was not
> >>> lowercase. Thanks to Pascal Heinrich.
> >>>        • LOG4J2-1852: Locate plugins within a Jar using a URL
> >>> Connection. Thanks to Tanner Altares.
> >>>        • LOG4J2-2610: Explicitly set file creation time.
> >>>        • LOG4J2-2561: JEP223 version detection fix for JDK 9 and up.
> >>> Thanks to Ulrich Enslin.
> >>>        • LOG4J2-1103: FailoverAppender was failing with ERROR appender
> >>> Failover has no parameter that matches element Failovers. Thanks to
> Seán
> >>> Dunne.
> >>>        • LOG4J2-2602: Update file time when size based triggering
> policy
> >>> is used without a time-based triggering policy.
> >>>        • LOG4J2-2597: Throw better exception message when both
> >>> log4j-slf4j-impl and log4j-to-slf4j are present.
> >>>        • LOG4J2-2559: NullPointerException in
> >>> JdbcAppender.createAppender(). Thanks to Li Lei, Gary Gregory.
> >>>        • LOG4J2-2592: StackOverflowException when server not reachable
> >>> with SocketAppender. Thanks to Dávid Kaya, Gary Gregory.
> >>>        • LOG4J2-2598: java.lang.StackOverflowError at
> >>>
> org.apache.logging.log4j.junit.AbstractExternalFileCleaner.println(AbstractExternalFileCleaner.java:169).
> >>> Thanks to Gary Gregory.
> >>>        • LOG4J2-2564: MapPatternConverter is properly created from the
> >>> '%K', '%map', and '%MAP' patterns. PatternConverter instanceOf methods
> with
> >>> unknown parameter types no longer elide those with known parameters.
> >>>        • LOG4J2-2612: NullPointerException at
> >>>
> org.apache.logging.log4j.core.appender.db.jdbc.JdbcDatabaseManager.writeInternal(JdbcDatabaseManager.java:803).
> >>>        • LOG4J2-2618: Possible ClassCastException in
> >>>
> org.apache.logging.log4j.core.script.ScriptManager.ScriptManager(Configuration,
> >>> WatchManager)
> >>>        • LOG4J2-2631: RoutingAppender PurgePolicy implementations no
> >>> longer stop appenders referenced from the logger configuration, only
> those
> >>> that have been created by the RoutingAppender. Note that
> >>> RoutingAppender.getAppenders no longer includes entries for referenced
> >>> appenders, only those which it has created.
> >>>        • LOG4J2-2629: Fix a race allowing events not to be recorded
> when
> >>> a RoutingAppender purge policy attempts to delete an idle appender at
> >>> exactly the same time as a new event is recorded.
> >>>        • LOG4J2-2606: Asynchronous logging when the queue is full no
> >>> longer results in heavy CPU utilization and low throughput.
> >>> Changes
> >>>
> >>>        • : Update tests from H2 1.4.197 to 1.4.199. Thanks to Gary
> >>> Gregory.
> >>>        • LOG4J2-2570: Update Jackson from 2.9.7 to 2.9.8. Thanks to
> Gary
> >>> Gregory.
> >>>        • LOG4J2-2574: Update MongoDB 3 module driver from 3.9.0 to
> >>> 3.10.1. Thanks to Gary Gregory.
> >>>        • LOG4J2-2619: Update Jackson from 2.9.8 to 2.9.9.
> >>>        • LOG4J2-2634: Refactor several AsyncLogger methods below the 35
> >>> byte threshold for inlining.
> >>>
> >>> Tag:
> >>> a)  for a new copy do "git clone
> >>> https://github.com/apache/logging-log4j2.git" and then "git checkout
> >>> tags/log4j-2.12.0-rc2”
> >>> b) for an existing working copy to “git pull” and then “git checkout
> >>> tags/log4j-2.12.0-rc2”
> >>>
> >>> Web Site:  http://rgoers.github.io/log4j2-site/index.html.
> >>>
> >>> Maven Artifacts:
> >>>
> https://repository.apache.org/content/repositories/orgapachelogging-1047
> >>>
> >>> Distribution archives:
> >>> https://dist.apache.org/repos/dist/dev/logging/log4j/
> >>>
> >>> You may download all the Maven artifacts by executing:
> >>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
> >>>
> https://repository.apache.org/content/repositories/orgapachelogging-1047/org/apache/logging/log4j/
> >>>
> >>> Ralph
> >>>
> >>
>
>
>

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Ralph Goers <ra...@dslextreme.com>.
I don’t run the build with Java 11, although I do have projects that use it that are on Java 11. It seems that log4j-api is failing when compiling with Java 11 because sun.reflect.Reflection was removed in Java 9.  I guess we need to modify the toolchains configuration to tell the main modules to use only Java 8 to compile.  The only other option would be to create a jar that has that class in it and specify it as a provided dependency.

Ralph

> On Jun 26, 2019, at 7:32 AM, Gary Gregory <ga...@gmail.com> wrote:
> 
> Driving me nuts: I can do the following OK on Java 8: " mvn -P rat
> -DskipTests clean install".
> But then I switch to Java 11 and run "mvn test" and Maven wants to
> recompile everything and fails as noted below.
> How do you test on Java 11?
> 
> Gary
> 
> On Wed, Jun 26, 2019 at 10:24 AM Gary Gregory <ga...@gmail.com>
> wrote:
> 
>> Note: Compiling on Java 11 fails:
>> 
>> [INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @
>> log4j-api ---
>> [INFO] Changes detected - recompiling the module!
>> [INFO] Compiling 84 source files to
>> C:\temp\rc\logging-log4j2\log4j-api\target\test-classes
>> [INFO] -------------------------------------------------------------
>> [WARNING] COMPILATION WARNING :
>> [INFO] -------------------------------------------------------------
>> [WARNING] [options] bootstrap class path not set in conjunction with
>> -source 7
>> [WARNING] No processor claimed any of these annotations:
>> org.junit.AfterClass,org.junit.Rule,org.junit.BeforeClass,org.junit.Ignore,org.junit.After,org.junit.runner.RunWith,org.junit.runners.Parameterized.Parameters,org.junit.Test,org.junit.ClassRule,org.junit.Before
>> [INFO] 2 warnings
>> [INFO] -------------------------------------------------------------
>> [INFO] -------------------------------------------------------------
>> [ERROR] COMPILATION ERROR :
>> [INFO] -------------------------------------------------------------
>> [ERROR]
>> C:\temp\rc\logging-log4j2\log4j-api\src\test\java\org\apache\logging\log4j\util\StackLocatorUtilTest.java:[25,18]
>> error: cannot find symbol
>>  symbol:   class Reflection
>>  location: package sun.reflect
>> [INFO] 1 error
>> [INFO] -------------------------------------------------------------
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Reactor Summary for Apache Log4j 2 2.12.0:
>> [INFO]
>> [INFO] Apache Log4j 2 ..................................... SUCCESS [
>> 3.167 s]
>> [INFO] Apache Log4j API Java 9 support .................... SUCCESS [
>> 6.356 s]
>> [INFO] Apache Log4j API ................................... FAILURE [
>> 10.530 s]
>> 
>> Gary
>> 
>> 
>> On Tue, Jun 25, 2019 at 11:59 PM Ralph Goers <ra...@dslextreme.com>
>> wrote:
>> 
>>> This is a vote to release Log4j 2.12.0, the next version of the Log4j 2
>>> project.
>>> 
>>> Please download, test, and cast your votes on the log4j developers list.
>>> [] +1, release the artifacts
>>> [] -1, don't release because...
>>> 
>>> The vote will remain open for 72 hours (or more if required). All votes
>>> are welcome and we encourage everyone to test the release, but only Logging
>>> PMC votes are “officially” counted. As always, at least 3 +1 votes and more
>>> positive than negative votes are required.
>>> 
>>> Changes in this release include:
>>> 
>>> New Features
>>> 
>>>        • LOG4J2-2403: Allow zero padding the counter of a
>>> RollingFileAppender. Thanks to hupfdule.
>>>        • LOG4J2-2427: Add filter that will match events when no marker
>>> is present. Thanks to Rimaljit Kaur.
>>>        • LOG4J2-2406: Add reconfiguration methods to Configurator.
>>>        • LOG4J2-913: Add support for reconfiguration via HTTP(S),
>>> Docker, and Spring Cloud Configuration.
>>>        • LOG4J2-2586: TCP Appender should support a host name resolving
>>> to multiple IP addresses.
>>>        • LOG4J2-2337: Allow custom end-of-line with JsonLayout. Thanks
>>> to Arvind Sahare, Patrice Ferrot.
>>>        • LOG4J2-2598: GZIP compression on rollover supports configurable
>>> compression levels. Thanks to Carter Kozak.
>>>        • LOG4J2-2611: AsyncQueueFullPolicy configuration short values
>>> "Default" and "Discard" are case insensitive to avoid confusion.
>>>        • LOG4J2-2634: Add and use method
>>> org.apache.logging.log4j.message.MapMessage.toKey(String) for simpler
>>> subclasses.
>>> Fixed Bugs
>>> 
>>>        • LOG4J2-2547: RollingRandomAccessFileAppender error message
>>> referenced incorrect class name.
>>>        • LOG4J2-2616: Restore constructor to ThrowablePatternConverter
>>> that was removed in 2.8.2.
>>>        • LOG4J2-2622: StructuredDataId was ignoring maxLength atribute.
>>>        • LOG4J2-2636: RFC5424Layout was not properly setting default
>>> Structured Element id for the MDC
>>>        • LOG4J2-1143: Lookups were not found if the plugin key was not
>>> lowercase. Thanks to Pascal Heinrich.
>>>        • LOG4J2-1852: Locate plugins within a Jar using a URL
>>> Connection. Thanks to Tanner Altares.
>>>        • LOG4J2-2610: Explicitly set file creation time.
>>>        • LOG4J2-2561: JEP223 version detection fix for JDK 9 and up.
>>> Thanks to Ulrich Enslin.
>>>        • LOG4J2-1103: FailoverAppender was failing with ERROR appender
>>> Failover has no parameter that matches element Failovers. Thanks to Seán
>>> Dunne.
>>>        • LOG4J2-2602: Update file time when size based triggering policy
>>> is used without a time-based triggering policy.
>>>        • LOG4J2-2597: Throw better exception message when both
>>> log4j-slf4j-impl and log4j-to-slf4j are present.
>>>        • LOG4J2-2559: NullPointerException in
>>> JdbcAppender.createAppender(). Thanks to Li Lei, Gary Gregory.
>>>        • LOG4J2-2592: StackOverflowException when server not reachable
>>> with SocketAppender. Thanks to Dávid Kaya, Gary Gregory.
>>>        • LOG4J2-2598: java.lang.StackOverflowError at
>>> org.apache.logging.log4j.junit.AbstractExternalFileCleaner.println(AbstractExternalFileCleaner.java:169).
>>> Thanks to Gary Gregory.
>>>        • LOG4J2-2564: MapPatternConverter is properly created from the
>>> '%K', '%map', and '%MAP' patterns. PatternConverter instanceOf methods with
>>> unknown parameter types no longer elide those with known parameters.
>>>        • LOG4J2-2612: NullPointerException at
>>> org.apache.logging.log4j.core.appender.db.jdbc.JdbcDatabaseManager.writeInternal(JdbcDatabaseManager.java:803).
>>>        • LOG4J2-2618: Possible ClassCastException in
>>> org.apache.logging.log4j.core.script.ScriptManager.ScriptManager(Configuration,
>>> WatchManager)
>>>        • LOG4J2-2631: RoutingAppender PurgePolicy implementations no
>>> longer stop appenders referenced from the logger configuration, only those
>>> that have been created by the RoutingAppender. Note that
>>> RoutingAppender.getAppenders no longer includes entries for referenced
>>> appenders, only those which it has created.
>>>        • LOG4J2-2629: Fix a race allowing events not to be recorded when
>>> a RoutingAppender purge policy attempts to delete an idle appender at
>>> exactly the same time as a new event is recorded.
>>>        • LOG4J2-2606: Asynchronous logging when the queue is full no
>>> longer results in heavy CPU utilization and low throughput.
>>> Changes
>>> 
>>>        • : Update tests from H2 1.4.197 to 1.4.199. Thanks to Gary
>>> Gregory.
>>>        • LOG4J2-2570: Update Jackson from 2.9.7 to 2.9.8. Thanks to Gary
>>> Gregory.
>>>        • LOG4J2-2574: Update MongoDB 3 module driver from 3.9.0 to
>>> 3.10.1. Thanks to Gary Gregory.
>>>        • LOG4J2-2619: Update Jackson from 2.9.8 to 2.9.9.
>>>        • LOG4J2-2634: Refactor several AsyncLogger methods below the 35
>>> byte threshold for inlining.
>>> 
>>> Tag:
>>> a)  for a new copy do "git clone
>>> https://github.com/apache/logging-log4j2.git" and then "git checkout
>>> tags/log4j-2.12.0-rc2”
>>> b) for an existing working copy to “git pull” and then “git checkout
>>> tags/log4j-2.12.0-rc2”
>>> 
>>> Web Site:  http://rgoers.github.io/log4j2-site/index.html.
>>> 
>>> Maven Artifacts:
>>> https://repository.apache.org/content/repositories/orgapachelogging-1047
>>> 
>>> Distribution archives:
>>> https://dist.apache.org/repos/dist/dev/logging/log4j/
>>> 
>>> You may download all the Maven artifacts by executing:
>>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
>>> https://repository.apache.org/content/repositories/orgapachelogging-1047/org/apache/logging/log4j/
>>> 
>>> Ralph
>>> 
>>

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Gary Gregory <ga...@gmail.com>.
Driving me nuts: I can do the following OK on Java 8: " mvn -P rat
-DskipTests clean install".
But then I switch to Java 11 and run "mvn test" and Maven wants to
recompile everything and fails as noted below.
How do you test on Java 11?

Gary

On Wed, Jun 26, 2019 at 10:24 AM Gary Gregory <ga...@gmail.com>
wrote:

> Note: Compiling on Java 11 fails:
>
> [INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @
> log4j-api ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 84 source files to
> C:\temp\rc\logging-log4j2\log4j-api\target\test-classes
> [INFO] -------------------------------------------------------------
> [WARNING] COMPILATION WARNING :
> [INFO] -------------------------------------------------------------
> [WARNING] [options] bootstrap class path not set in conjunction with
> -source 7
> [WARNING] No processor claimed any of these annotations:
> org.junit.AfterClass,org.junit.Rule,org.junit.BeforeClass,org.junit.Ignore,org.junit.After,org.junit.runner.RunWith,org.junit.runners.Parameterized.Parameters,org.junit.Test,org.junit.ClassRule,org.junit.Before
> [INFO] 2 warnings
> [INFO] -------------------------------------------------------------
> [INFO] -------------------------------------------------------------
> [ERROR] COMPILATION ERROR :
> [INFO] -------------------------------------------------------------
> [ERROR]
> C:\temp\rc\logging-log4j2\log4j-api\src\test\java\org\apache\logging\log4j\util\StackLocatorUtilTest.java:[25,18]
> error: cannot find symbol
>   symbol:   class Reflection
>   location: package sun.reflect
> [INFO] 1 error
> [INFO] -------------------------------------------------------------
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary for Apache Log4j 2 2.12.0:
> [INFO]
> [INFO] Apache Log4j 2 ..................................... SUCCESS [
>  3.167 s]
> [INFO] Apache Log4j API Java 9 support .................... SUCCESS [
>  6.356 s]
> [INFO] Apache Log4j API ................................... FAILURE [
> 10.530 s]
>
> Gary
>
>
> On Tue, Jun 25, 2019 at 11:59 PM Ralph Goers <ra...@dslextreme.com>
> wrote:
>
>> This is a vote to release Log4j 2.12.0, the next version of the Log4j 2
>> project.
>>
>> Please download, test, and cast your votes on the log4j developers list.
>> [] +1, release the artifacts
>> [] -1, don't release because...
>>
>> The vote will remain open for 72 hours (or more if required). All votes
>> are welcome and we encourage everyone to test the release, but only Logging
>> PMC votes are “officially” counted. As always, at least 3 +1 votes and more
>> positive than negative votes are required.
>>
>> Changes in this release include:
>>
>> New Features
>>
>>         • LOG4J2-2403: Allow zero padding the counter of a
>> RollingFileAppender. Thanks to hupfdule.
>>         • LOG4J2-2427: Add filter that will match events when no marker
>> is present. Thanks to Rimaljit Kaur.
>>         • LOG4J2-2406: Add reconfiguration methods to Configurator.
>>         • LOG4J2-913: Add support for reconfiguration via HTTP(S),
>> Docker, and Spring Cloud Configuration.
>>         • LOG4J2-2586: TCP Appender should support a host name resolving
>> to multiple IP addresses.
>>         • LOG4J2-2337: Allow custom end-of-line with JsonLayout. Thanks
>> to Arvind Sahare, Patrice Ferrot.
>>         • LOG4J2-2598: GZIP compression on rollover supports configurable
>> compression levels. Thanks to Carter Kozak.
>>         • LOG4J2-2611: AsyncQueueFullPolicy configuration short values
>> "Default" and "Discard" are case insensitive to avoid confusion.
>>         • LOG4J2-2634: Add and use method
>> org.apache.logging.log4j.message.MapMessage.toKey(String) for simpler
>> subclasses.
>> Fixed Bugs
>>
>>         • LOG4J2-2547: RollingRandomAccessFileAppender error message
>> referenced incorrect class name.
>>         • LOG4J2-2616: Restore constructor to ThrowablePatternConverter
>> that was removed in 2.8.2.
>>         • LOG4J2-2622: StructuredDataId was ignoring maxLength atribute.
>>         • LOG4J2-2636: RFC5424Layout was not properly setting default
>> Structured Element id for the MDC
>>         • LOG4J2-1143: Lookups were not found if the plugin key was not
>> lowercase. Thanks to Pascal Heinrich.
>>         • LOG4J2-1852: Locate plugins within a Jar using a URL
>> Connection. Thanks to Tanner Altares.
>>         • LOG4J2-2610: Explicitly set file creation time.
>>         • LOG4J2-2561: JEP223 version detection fix for JDK 9 and up.
>> Thanks to Ulrich Enslin.
>>         • LOG4J2-1103: FailoverAppender was failing with ERROR appender
>> Failover has no parameter that matches element Failovers. Thanks to Seán
>> Dunne.
>>         • LOG4J2-2602: Update file time when size based triggering policy
>> is used without a time-based triggering policy.
>>         • LOG4J2-2597: Throw better exception message when both
>> log4j-slf4j-impl and log4j-to-slf4j are present.
>>         • LOG4J2-2559: NullPointerException in
>> JdbcAppender.createAppender(). Thanks to Li Lei, Gary Gregory.
>>         • LOG4J2-2592: StackOverflowException when server not reachable
>> with SocketAppender. Thanks to Dávid Kaya, Gary Gregory.
>>         • LOG4J2-2598: java.lang.StackOverflowError at
>> org.apache.logging.log4j.junit.AbstractExternalFileCleaner.println(AbstractExternalFileCleaner.java:169).
>> Thanks to Gary Gregory.
>>         • LOG4J2-2564: MapPatternConverter is properly created from the
>> '%K', '%map', and '%MAP' patterns. PatternConverter instanceOf methods with
>> unknown parameter types no longer elide those with known parameters.
>>         • LOG4J2-2612: NullPointerException at
>> org.apache.logging.log4j.core.appender.db.jdbc.JdbcDatabaseManager.writeInternal(JdbcDatabaseManager.java:803).
>>         • LOG4J2-2618: Possible ClassCastException in
>> org.apache.logging.log4j.core.script.ScriptManager.ScriptManager(Configuration,
>> WatchManager)
>>         • LOG4J2-2631: RoutingAppender PurgePolicy implementations no
>> longer stop appenders referenced from the logger configuration, only those
>> that have been created by the RoutingAppender. Note that
>> RoutingAppender.getAppenders no longer includes entries for referenced
>> appenders, only those which it has created.
>>         • LOG4J2-2629: Fix a race allowing events not to be recorded when
>> a RoutingAppender purge policy attempts to delete an idle appender at
>> exactly the same time as a new event is recorded.
>>         • LOG4J2-2606: Asynchronous logging when the queue is full no
>> longer results in heavy CPU utilization and low throughput.
>> Changes
>>
>>         • : Update tests from H2 1.4.197 to 1.4.199. Thanks to Gary
>> Gregory.
>>         • LOG4J2-2570: Update Jackson from 2.9.7 to 2.9.8. Thanks to Gary
>> Gregory.
>>         • LOG4J2-2574: Update MongoDB 3 module driver from 3.9.0 to
>> 3.10.1. Thanks to Gary Gregory.
>>         • LOG4J2-2619: Update Jackson from 2.9.8 to 2.9.9.
>>         • LOG4J2-2634: Refactor several AsyncLogger methods below the 35
>> byte threshold for inlining.
>>
>> Tag:
>> a)  for a new copy do "git clone
>> https://github.com/apache/logging-log4j2.git" and then "git checkout
>> tags/log4j-2.12.0-rc2”
>> b) for an existing working copy to “git pull” and then “git checkout
>> tags/log4j-2.12.0-rc2”
>>
>> Web Site:  http://rgoers.github.io/log4j2-site/index.html.
>>
>> Maven Artifacts:
>> https://repository.apache.org/content/repositories/orgapachelogging-1047
>>
>> Distribution archives:
>> https://dist.apache.org/repos/dist/dev/logging/log4j/
>>
>> You may download all the Maven artifacts by executing:
>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
>> https://repository.apache.org/content/repositories/orgapachelogging-1047/org/apache/logging/log4j/
>>
>> Ralph
>>
>

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Gary Gregory <ga...@gmail.com>.
Note: Compiling on Java 11 fails:

[INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @
log4j-api ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 84 source files to
C:\temp\rc\logging-log4j2\log4j-api\target\test-classes
[INFO] -------------------------------------------------------------
[WARNING] COMPILATION WARNING :
[INFO] -------------------------------------------------------------
[WARNING] [options] bootstrap class path not set in conjunction with
-source 7
[WARNING] No processor claimed any of these annotations:
org.junit.AfterClass,org.junit.Rule,org.junit.BeforeClass,org.junit.Ignore,org.junit.After,org.junit.runner.RunWith,org.junit.runners.Parameterized.Parameters,org.junit.Test,org.junit.ClassRule,org.junit.Before
[INFO] 2 warnings
[INFO] -------------------------------------------------------------
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR]
C:\temp\rc\logging-log4j2\log4j-api\src\test\java\org\apache\logging\log4j\util\StackLocatorUtilTest.java:[25,18]
error: cannot find symbol
  symbol:   class Reflection
  location: package sun.reflect
[INFO] 1 error
[INFO] -------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary for Apache Log4j 2 2.12.0:
[INFO]
[INFO] Apache Log4j 2 ..................................... SUCCESS [
 3.167 s]
[INFO] Apache Log4j API Java 9 support .................... SUCCESS [
 6.356 s]
[INFO] Apache Log4j API ................................... FAILURE [
10.530 s]

Gary


On Tue, Jun 25, 2019 at 11:59 PM Ralph Goers <ra...@dslextreme.com>
wrote:

> This is a vote to release Log4j 2.12.0, the next version of the Log4j 2
> project.
>
> Please download, test, and cast your votes on the log4j developers list.
> [] +1, release the artifacts
> [] -1, don't release because...
>
> The vote will remain open for 72 hours (or more if required). All votes
> are welcome and we encourage everyone to test the release, but only Logging
> PMC votes are “officially” counted. As always, at least 3 +1 votes and more
> positive than negative votes are required.
>
> Changes in this release include:
>
> New Features
>
>         • LOG4J2-2403: Allow zero padding the counter of a
> RollingFileAppender. Thanks to hupfdule.
>         • LOG4J2-2427: Add filter that will match events when no marker is
> present. Thanks to Rimaljit Kaur.
>         • LOG4J2-2406: Add reconfiguration methods to Configurator.
>         • LOG4J2-913: Add support for reconfiguration via HTTP(S), Docker,
> and Spring Cloud Configuration.
>         • LOG4J2-2586: TCP Appender should support a host name resolving
> to multiple IP addresses.
>         • LOG4J2-2337: Allow custom end-of-line with JsonLayout. Thanks to
> Arvind Sahare, Patrice Ferrot.
>         • LOG4J2-2598: GZIP compression on rollover supports configurable
> compression levels. Thanks to Carter Kozak.
>         • LOG4J2-2611: AsyncQueueFullPolicy configuration short values
> "Default" and "Discard" are case insensitive to avoid confusion.
>         • LOG4J2-2634: Add and use method
> org.apache.logging.log4j.message.MapMessage.toKey(String) for simpler
> subclasses.
> Fixed Bugs
>
>         • LOG4J2-2547: RollingRandomAccessFileAppender error message
> referenced incorrect class name.
>         • LOG4J2-2616: Restore constructor to ThrowablePatternConverter
> that was removed in 2.8.2.
>         • LOG4J2-2622: StructuredDataId was ignoring maxLength atribute.
>         • LOG4J2-2636: RFC5424Layout was not properly setting default
> Structured Element id for the MDC
>         • LOG4J2-1143: Lookups were not found if the plugin key was not
> lowercase. Thanks to Pascal Heinrich.
>         • LOG4J2-1852: Locate plugins within a Jar using a URL Connection.
> Thanks to Tanner Altares.
>         • LOG4J2-2610: Explicitly set file creation time.
>         • LOG4J2-2561: JEP223 version detection fix for JDK 9 and up.
> Thanks to Ulrich Enslin.
>         • LOG4J2-1103: FailoverAppender was failing with ERROR appender
> Failover has no parameter that matches element Failovers. Thanks to Seán
> Dunne.
>         • LOG4J2-2602: Update file time when size based triggering policy
> is used without a time-based triggering policy.
>         • LOG4J2-2597: Throw better exception message when both
> log4j-slf4j-impl and log4j-to-slf4j are present.
>         • LOG4J2-2559: NullPointerException in
> JdbcAppender.createAppender(). Thanks to Li Lei, Gary Gregory.
>         • LOG4J2-2592: StackOverflowException when server not reachable
> with SocketAppender. Thanks to Dávid Kaya, Gary Gregory.
>         • LOG4J2-2598: java.lang.StackOverflowError at
> org.apache.logging.log4j.junit.AbstractExternalFileCleaner.println(AbstractExternalFileCleaner.java:169).
> Thanks to Gary Gregory.
>         • LOG4J2-2564: MapPatternConverter is properly created from the
> '%K', '%map', and '%MAP' patterns. PatternConverter instanceOf methods with
> unknown parameter types no longer elide those with known parameters.
>         • LOG4J2-2612: NullPointerException at
> org.apache.logging.log4j.core.appender.db.jdbc.JdbcDatabaseManager.writeInternal(JdbcDatabaseManager.java:803).
>         • LOG4J2-2618: Possible ClassCastException in
> org.apache.logging.log4j.core.script.ScriptManager.ScriptManager(Configuration,
> WatchManager)
>         • LOG4J2-2631: RoutingAppender PurgePolicy implementations no
> longer stop appenders referenced from the logger configuration, only those
> that have been created by the RoutingAppender. Note that
> RoutingAppender.getAppenders no longer includes entries for referenced
> appenders, only those which it has created.
>         • LOG4J2-2629: Fix a race allowing events not to be recorded when
> a RoutingAppender purge policy attempts to delete an idle appender at
> exactly the same time as a new event is recorded.
>         • LOG4J2-2606: Asynchronous logging when the queue is full no
> longer results in heavy CPU utilization and low throughput.
> Changes
>
>         • : Update tests from H2 1.4.197 to 1.4.199. Thanks to Gary
> Gregory.
>         • LOG4J2-2570: Update Jackson from 2.9.7 to 2.9.8. Thanks to Gary
> Gregory.
>         • LOG4J2-2574: Update MongoDB 3 module driver from 3.9.0 to
> 3.10.1. Thanks to Gary Gregory.
>         • LOG4J2-2619: Update Jackson from 2.9.8 to 2.9.9.
>         • LOG4J2-2634: Refactor several AsyncLogger methods below the 35
> byte threshold for inlining.
>
> Tag:
> a)  for a new copy do "git clone
> https://github.com/apache/logging-log4j2.git" and then "git checkout
> tags/log4j-2.12.0-rc2”
> b) for an existing working copy to “git pull” and then “git checkout
> tags/log4j-2.12.0-rc2”
>
> Web Site:  http://rgoers.github.io/log4j2-site/index.html.
>
> Maven Artifacts:
> https://repository.apache.org/content/repositories/orgapachelogging-1047
>
> Distribution archives:
> https://dist.apache.org/repos/dist/dev/logging/log4j/
>
> You may download all the Maven artifacts by executing:
> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
> https://repository.apache.org/content/repositories/orgapachelogging-1047/org/apache/logging/log4j/
>
> Ralph
>

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Carter Kozak <ck...@ckozak.net>.
+1 from me, if there are issues on java 11 we can release another build. I agree that we should put some time into getting CI running on both minimum and maximum supported jvms, but that doesn't need to block this release. I have no reason to believe that 2.12.0 has regressed from 2.11.2, and I have verified functionality on services running java 8 and 11.

Thanks,
-ck

On Fri, Jun 28, 2019, at 15:49, Ralph Goers wrote:
> Oops. I jumped the gun. There are still a little less than 8 hours before 72 hours will have elapsed.
> 
> Ralph
> 
> > On Jun 28, 2019, at 12:47 PM, Ralph Goers <ra...@dslextreme.com> wrote:
> > 
> > For the record, here is my +1. 72 hours has elapsed but one more vote is needed for the release to proceed.
> > 
> > Ralph
> > 
> >> On Jun 25, 2019, at 8:59 PM, Ralph Goers <ra...@dslextreme.com> wrote:
> >> 
> >> This is a vote to release Log4j 2.12.0, the next version of the Log4j 2 project.
> >> 
> >> Please download, test, and cast your votes on the log4j developers list.
> >> [] +1, release the artifacts
> >> [] -1, don't release because...
> >> 
> >> The vote will remain open for 72 hours (or more if required). All votes are welcome and we encourage everyone to test the release, but only Logging PMC votes are “officially” counted. As always, at least 3 +1 votes and more positive than negative votes are required.
> >> 
> >> Changes in this release include:
> >> 
> >> New Features
> >> 
> >> • LOG4J2-2403: Allow zero padding the counter of a RollingFileAppender. Thanks to hupfdule.
> >> • LOG4J2-2427: Add filter that will match events when no marker is present. Thanks to Rimaljit Kaur.
> >> • LOG4J2-2406: Add reconfiguration methods to Configurator.
> >> • LOG4J2-913: Add support for reconfiguration via HTTP(S), Docker, and Spring Cloud Configuration.
> >> • LOG4J2-2586: TCP Appender should support a host name resolving to multiple IP addresses.
> >> • LOG4J2-2337: Allow custom end-of-line with JsonLayout. Thanks to Arvind Sahare, Patrice Ferrot.
> >> • LOG4J2-2598: GZIP compression on rollover supports configurable compression levels. Thanks to Carter Kozak.
> >> • LOG4J2-2611: AsyncQueueFullPolicy configuration short values "Default" and "Discard" are case insensitive to avoid confusion.
> >> • LOG4J2-2634: Add and use method org.apache.logging.log4j.message.MapMessage.toKey(String) for simpler subclasses.
> >> Fixed Bugs
> >> 
> >> • LOG4J2-2547: RollingRandomAccessFileAppender error message referenced incorrect class name.
> >> • LOG4J2-2616: Restore constructor to ThrowablePatternConverter that was removed in 2.8.2.
> >> • LOG4J2-2622: StructuredDataId was ignoring maxLength atribute.
> >> • LOG4J2-2636: RFC5424Layout was not properly setting default Structured Element id for the MDC
> >> • LOG4J2-1143: Lookups were not found if the plugin key was not lowercase. Thanks to Pascal Heinrich.
> >> • LOG4J2-1852: Locate plugins within a Jar using a URL Connection. Thanks to Tanner Altares.
> >> • LOG4J2-2610: Explicitly set file creation time.
> >> • LOG4J2-2561: JEP223 version detection fix for JDK 9 and up. Thanks to Ulrich Enslin.
> >> • LOG4J2-1103: FailoverAppender was failing with ERROR appender Failover has no parameter that matches element Failovers. Thanks to Seán Dunne.
> >> • LOG4J2-2602: Update file time when size based triggering policy is used without a time-based triggering policy.
> >> • LOG4J2-2597: Throw better exception message when both log4j-slf4j-impl and log4j-to-slf4j are present.
> >> • LOG4J2-2559: NullPointerException in JdbcAppender.createAppender(). Thanks to Li Lei, Gary Gregory.
> >> • LOG4J2-2592: StackOverflowException when server not reachable with SocketAppender. Thanks to Dávid Kaya, Gary Gregory.
> >> • LOG4J2-2598: java.lang.StackOverflowError at org.apache.logging.log4j.junit.AbstractExternalFileCleaner.println(AbstractExternalFileCleaner.java:169). Thanks to Gary Gregory.
> >> • LOG4J2-2564: MapPatternConverter is properly created from the '%K', '%map', and '%MAP' patterns. PatternConverter instanceOf methods with unknown parameter types no longer elide those with known parameters.
> >> • LOG4J2-2612: NullPointerException at org.apache.logging.log4j.core.appender.db.jdbc.JdbcDatabaseManager.writeInternal(JdbcDatabaseManager.java:803).
> >> • LOG4J2-2618: Possible ClassCastException in org.apache.logging.log4j.core.script.ScriptManager.ScriptManager(Configuration, WatchManager)
> >> • LOG4J2-2631: RoutingAppender PurgePolicy implementations no longer stop appenders referenced from the logger configuration, only those that have been created by the RoutingAppender. Note that RoutingAppender.getAppenders no longer includes entries for referenced appenders, only those which it has created.
> >> • LOG4J2-2629: Fix a race allowing events not to be recorded when a RoutingAppender purge policy attempts to delete an idle appender at exactly the same time as a new event is recorded.
> >> • LOG4J2-2606: Asynchronous logging when the queue is full no longer results in heavy CPU utilization and low throughput.
> >> Changes
> >> 
> >> • : Update tests from H2 1.4.197 to 1.4.199. Thanks to Gary Gregory.
> >> • LOG4J2-2570: Update Jackson from 2.9.7 to 2.9.8. Thanks to Gary Gregory.
> >> • LOG4J2-2574: Update MongoDB 3 module driver from 3.9.0 to 3.10.1. Thanks to Gary Gregory.
> >> • LOG4J2-2619: Update Jackson from 2.9.8 to 2.9.9.
> >> • LOG4J2-2634: Refactor several AsyncLogger methods below the 35 byte threshold for inlining.
> >> 
> >> Tag: 
> >> a) for a new copy do "git clone https://github.com/apache/logging-log4j2.git" and then "git checkout tags/log4j-2.12.0-rc2” 
> >> b) for an existing working copy to “git pull” and then “git checkout tags/log4j-2.12.0-rc2”
> >> 
> >> Web Site: http://rgoers.github.io/log4j2-site/index.html.
> >> 
> >> Maven Artifacts: https://repository.apache.org/content/repositories/orgapachelogging-1047
> >> 
> >> Distribution archives: https://dist.apache.org/repos/dist/dev/logging/log4j/ 
> >> 
> >> You may download all the Maven artifacts by executing:
> >> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate https://repository.apache.org/content/repositories/orgapachelogging-1047/org/apache/logging/log4j/
> >> 
> >> Ralph
> >> 
> > 
> > 
> > 
> 
> 
>

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Ralph Goers <ra...@dslextreme.com>.
Oops. I jumped the gun. There are still a little less than 8 hours before 72 hours will have elapsed.

Ralph

> On Jun 28, 2019, at 12:47 PM, Ralph Goers <ra...@dslextreme.com> wrote:
> 
> For the record, here is my +1.  72 hours has elapsed but one more vote is needed for the release to proceed.
> 
> Ralph
> 
>> On Jun 25, 2019, at 8:59 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>> 
>> This is a vote to release Log4j 2.12.0, the next version of the Log4j 2 project.
>> 
>> Please download, test, and cast your votes on the log4j developers list.
>> [] +1, release the artifacts
>> [] -1, don't release because...
>> 
>> The vote will remain open for 72 hours (or more if required). All votes are welcome and we encourage everyone to test the release, but only Logging PMC votes are “officially” counted. As always, at least 3 +1 votes and more positive than negative votes are required.
>> 
>> Changes in this release include:
>> 
>> New Features
>> 
>> 	• LOG4J2-2403: Allow zero padding the counter of a RollingFileAppender. Thanks to hupfdule.
>> 	• LOG4J2-2427: Add filter that will match events when no marker is present. Thanks to Rimaljit Kaur.
>> 	• LOG4J2-2406: Add reconfiguration methods to Configurator.
>> 	• LOG4J2-913: Add support for reconfiguration via HTTP(S), Docker, and Spring Cloud Configuration.
>> 	• LOG4J2-2586: TCP Appender should support a host name resolving to multiple IP addresses.
>> 	• LOG4J2-2337: Allow custom end-of-line with JsonLayout. Thanks to Arvind Sahare, Patrice Ferrot.
>> 	• LOG4J2-2598: GZIP compression on rollover supports configurable compression levels. Thanks to Carter Kozak.
>> 	• LOG4J2-2611: AsyncQueueFullPolicy configuration short values "Default" and "Discard" are case insensitive to avoid confusion.
>> 	• LOG4J2-2634: Add and use method org.apache.logging.log4j.message.MapMessage.toKey(String) for simpler subclasses.
>> Fixed Bugs
>> 
>> 	• LOG4J2-2547: RollingRandomAccessFileAppender error message referenced incorrect class name.
>> 	• LOG4J2-2616: Restore constructor to ThrowablePatternConverter that was removed in 2.8.2.
>> 	• LOG4J2-2622: StructuredDataId was ignoring maxLength atribute.
>> 	• LOG4J2-2636: RFC5424Layout was not properly setting default Structured Element id for the MDC
>> 	• LOG4J2-1143: Lookups were not found if the plugin key was not lowercase. Thanks to Pascal Heinrich.
>> 	• LOG4J2-1852: Locate plugins within a Jar using a URL Connection. Thanks to Tanner Altares.
>> 	• LOG4J2-2610: Explicitly set file creation time.
>> 	• LOG4J2-2561: JEP223 version detection fix for JDK 9 and up. Thanks to Ulrich Enslin.
>> 	• LOG4J2-1103: FailoverAppender was failing with ERROR appender Failover has no parameter that matches element Failovers. Thanks to Seán Dunne.
>> 	• LOG4J2-2602: Update file time when size based triggering policy is used without a time-based triggering policy.
>> 	• LOG4J2-2597: Throw better exception message when both log4j-slf4j-impl and log4j-to-slf4j are present.
>> 	• LOG4J2-2559: NullPointerException in JdbcAppender.createAppender(). Thanks to Li Lei, Gary Gregory.
>> 	• LOG4J2-2592: StackOverflowException when server not reachable with SocketAppender. Thanks to Dávid Kaya, Gary Gregory.
>> 	• LOG4J2-2598: java.lang.StackOverflowError at org.apache.logging.log4j.junit.AbstractExternalFileCleaner.println(AbstractExternalFileCleaner.java:169). Thanks to Gary Gregory.
>> 	• LOG4J2-2564: MapPatternConverter is properly created from the '%K', '%map', and '%MAP' patterns. PatternConverter instanceOf methods with unknown parameter types no longer elide those with known parameters.
>> 	• LOG4J2-2612: NullPointerException at org.apache.logging.log4j.core.appender.db.jdbc.JdbcDatabaseManager.writeInternal(JdbcDatabaseManager.java:803).
>> 	• LOG4J2-2618: Possible ClassCastException in org.apache.logging.log4j.core.script.ScriptManager.ScriptManager(Configuration, WatchManager)
>> 	• LOG4J2-2631: RoutingAppender PurgePolicy implementations no longer stop appenders referenced from the logger configuration, only those that have been created by the RoutingAppender. Note that RoutingAppender.getAppenders no longer includes entries for referenced appenders, only those which it has created.
>> 	• LOG4J2-2629: Fix a race allowing events not to be recorded when a RoutingAppender purge policy attempts to delete an idle appender at exactly the same time as a new event is recorded.
>> 	• LOG4J2-2606: Asynchronous logging when the queue is full no longer results in heavy CPU utilization and low throughput.
>> Changes
>> 
>> 	• : Update tests from H2 1.4.197 to 1.4.199. Thanks to Gary Gregory.
>> 	• LOG4J2-2570: Update Jackson from 2.9.7 to 2.9.8. Thanks to Gary Gregory.
>> 	• LOG4J2-2574: Update MongoDB 3 module driver from 3.9.0 to 3.10.1. Thanks to Gary Gregory.
>> 	• LOG4J2-2619: Update Jackson from 2.9.8 to 2.9.9.
>> 	• LOG4J2-2634: Refactor several AsyncLogger methods below the 35 byte threshold for inlining.
>> 
>> Tag: 
>> a)  for a new copy do "git clone https://github.com/apache/logging-log4j2.git" and then "git checkout tags/log4j-2.12.0-rc2” 
>> b) for an existing working copy to “git pull” and then “git checkout tags/log4j-2.12.0-rc2”
>> 
>> Web Site:  http://rgoers.github.io/log4j2-site/index.html.
>> 
>> Maven Artifacts: https://repository.apache.org/content/repositories/orgapachelogging-1047
>> 
>> Distribution archives: https://dist.apache.org/repos/dist/dev/logging/log4j/ 
>> 
>> You may download all the Maven artifacts by executing:
>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate https://repository.apache.org/content/repositories/orgapachelogging-1047/org/apache/logging/log4j/
>> 
>> Ralph
>> 
> 
> 
>

Re: [VOTE] Release Log4j 2.12.0-rc2

Posted by Ralph Goers <ra...@dslextreme.com>.
For the record, here is my +1.  72 hours has elapsed but one more vote is needed for the release to proceed.

Ralph

> On Jun 25, 2019, at 8:59 PM, Ralph Goers <ra...@dslextreme.com> wrote:
> 
> This is a vote to release Log4j 2.12.0, the next version of the Log4j 2 project.
> 
> Please download, test, and cast your votes on the log4j developers list.
> [] +1, release the artifacts
> [] -1, don't release because...
> 
> The vote will remain open for 72 hours (or more if required). All votes are welcome and we encourage everyone to test the release, but only Logging PMC votes are “officially” counted. As always, at least 3 +1 votes and more positive than negative votes are required.
> 
> Changes in this release include:
> 
> New Features
> 
> 	• LOG4J2-2403: Allow zero padding the counter of a RollingFileAppender. Thanks to hupfdule.
> 	• LOG4J2-2427: Add filter that will match events when no marker is present. Thanks to Rimaljit Kaur.
> 	• LOG4J2-2406: Add reconfiguration methods to Configurator.
> 	• LOG4J2-913: Add support for reconfiguration via HTTP(S), Docker, and Spring Cloud Configuration.
> 	• LOG4J2-2586: TCP Appender should support a host name resolving to multiple IP addresses.
> 	• LOG4J2-2337: Allow custom end-of-line with JsonLayout. Thanks to Arvind Sahare, Patrice Ferrot.
> 	• LOG4J2-2598: GZIP compression on rollover supports configurable compression levels. Thanks to Carter Kozak.
> 	• LOG4J2-2611: AsyncQueueFullPolicy configuration short values "Default" and "Discard" are case insensitive to avoid confusion.
> 	• LOG4J2-2634: Add and use method org.apache.logging.log4j.message.MapMessage.toKey(String) for simpler subclasses.
> Fixed Bugs
> 
> 	• LOG4J2-2547: RollingRandomAccessFileAppender error message referenced incorrect class name.
> 	• LOG4J2-2616: Restore constructor to ThrowablePatternConverter that was removed in 2.8.2.
> 	• LOG4J2-2622: StructuredDataId was ignoring maxLength atribute.
> 	• LOG4J2-2636: RFC5424Layout was not properly setting default Structured Element id for the MDC
> 	• LOG4J2-1143: Lookups were not found if the plugin key was not lowercase. Thanks to Pascal Heinrich.
> 	• LOG4J2-1852: Locate plugins within a Jar using a URL Connection. Thanks to Tanner Altares.
> 	• LOG4J2-2610: Explicitly set file creation time.
> 	• LOG4J2-2561: JEP223 version detection fix for JDK 9 and up. Thanks to Ulrich Enslin.
> 	• LOG4J2-1103: FailoverAppender was failing with ERROR appender Failover has no parameter that matches element Failovers. Thanks to Seán Dunne.
> 	• LOG4J2-2602: Update file time when size based triggering policy is used without a time-based triggering policy.
> 	• LOG4J2-2597: Throw better exception message when both log4j-slf4j-impl and log4j-to-slf4j are present.
> 	• LOG4J2-2559: NullPointerException in JdbcAppender.createAppender(). Thanks to Li Lei, Gary Gregory.
> 	• LOG4J2-2592: StackOverflowException when server not reachable with SocketAppender. Thanks to Dávid Kaya, Gary Gregory.
> 	• LOG4J2-2598: java.lang.StackOverflowError at org.apache.logging.log4j.junit.AbstractExternalFileCleaner.println(AbstractExternalFileCleaner.java:169). Thanks to Gary Gregory.
> 	• LOG4J2-2564: MapPatternConverter is properly created from the '%K', '%map', and '%MAP' patterns. PatternConverter instanceOf methods with unknown parameter types no longer elide those with known parameters.
> 	• LOG4J2-2612: NullPointerException at org.apache.logging.log4j.core.appender.db.jdbc.JdbcDatabaseManager.writeInternal(JdbcDatabaseManager.java:803).
> 	• LOG4J2-2618: Possible ClassCastException in org.apache.logging.log4j.core.script.ScriptManager.ScriptManager(Configuration, WatchManager)
> 	• LOG4J2-2631: RoutingAppender PurgePolicy implementations no longer stop appenders referenced from the logger configuration, only those that have been created by the RoutingAppender. Note that RoutingAppender.getAppenders no longer includes entries for referenced appenders, only those which it has created.
> 	• LOG4J2-2629: Fix a race allowing events not to be recorded when a RoutingAppender purge policy attempts to delete an idle appender at exactly the same time as a new event is recorded.
> 	• LOG4J2-2606: Asynchronous logging when the queue is full no longer results in heavy CPU utilization and low throughput.
> Changes
> 
> 	• : Update tests from H2 1.4.197 to 1.4.199. Thanks to Gary Gregory.
> 	• LOG4J2-2570: Update Jackson from 2.9.7 to 2.9.8. Thanks to Gary Gregory.
> 	• LOG4J2-2574: Update MongoDB 3 module driver from 3.9.0 to 3.10.1. Thanks to Gary Gregory.
> 	• LOG4J2-2619: Update Jackson from 2.9.8 to 2.9.9.
> 	• LOG4J2-2634: Refactor several AsyncLogger methods below the 35 byte threshold for inlining.
> 
> Tag: 
> a)  for a new copy do "git clone https://github.com/apache/logging-log4j2.git" and then "git checkout tags/log4j-2.12.0-rc2” 
> b) for an existing working copy to “git pull” and then “git checkout tags/log4j-2.12.0-rc2”
> 
> Web Site:  http://rgoers.github.io/log4j2-site/index.html.
> 
> Maven Artifacts: https://repository.apache.org/content/repositories/orgapachelogging-1047
> 
> Distribution archives: https://dist.apache.org/repos/dist/dev/logging/log4j/ 
> 
> You may download all the Maven artifacts by executing:
> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate https://repository.apache.org/content/repositories/orgapachelogging-1047/org/apache/logging/log4j/
> 
> Ralph
>