[jira] [Comment Edited] (LOG4J2-2002) DefaultConfigurationBuilder.writeXmlAttributes does not handle null attribute values

2017-08-27 Thread Paul Burrowes (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143353#comment-16143353 ] Paul Burrowes edited comment on LOG4J2-2002 at 8/28/17 4:26 AM: ---

[jira] [Commented] (LOG4J2-2002) DefaultConfigurationBuilder.writeXmlAttributes does not handle null attribute values

2017-08-27 Thread Paul Burrowes (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143353#comment-16143353 ] Paul Burrowes commented on LOG4J2-2002: --- Logger configuration is one that can accep

[jira] [Comment Edited] (LOG4J2-2005) Level.valueOf() converts level strings to uppercase

2017-08-27 Thread Paul Burrowes (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143352#comment-16143352 ] Paul Burrowes edited comment on LOG4J2-2005 at 8/28/17 4:22 AM: ---

[jira] [Commented] (LOG4J2-2005) Level.valueOf() converts level strings to uppercase

2017-08-27 Thread Paul Burrowes (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143352#comment-16143352 ] Paul Burrowes commented on LOG4J2-2005: --- Yes, case-insensitive comparison is accept

[jira] [Commented] (LOG4J2-2000) Highlight converter converts levels to uppercase before lookup

2017-08-27 Thread Paul Burrowes (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143351#comment-16143351 ] Paul Burrowes commented on LOG4J2-2000: --- Unfortunately, no, the constants in that c

Re: [VOTE] Release Log4j 2.9.0-rc1

2017-08-27 Thread Matt Sicker
On 27 August 2017 at 11:23, Ralph Goers wrote: > Matt added an exclude for the docker file back before the 2.8. release. > I’m not sure why. > I don't remember exactly why, but my guess is a rat-check error. The license header wasn't added until after 2.8 according to the tags: https://github.c

Re: [VOTE] Release Log4j 2.9.0-rc1

2017-08-27 Thread Ralph Goers
The KEYS file is where it has been since 2013 - https://dist.apache.org/repos/dist/release/logging/KEYS . This is documented at http://logging.apache.org/log4j/2.x/download.html . Ralph

Re: [VOTE] Release Log4j 2.9.0-rc1

2017-08-27 Thread Gary Gregory
+1 See my previous messages for details. Tested with: Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T13:39:06-06:00) Maven home: C:\Java\apache-maven-3.5.0\bin\.. Java version: 1.7.0_80, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.7.0_80\jre Default

Re: [VOTE] Release Log4j 2.9.0-rc1

2017-08-27 Thread Ralph Goers
With regard to the CLIRR report: 1. The change the return type from a MapMessage to a StructuredDataMessage was done by you on June 6. It isn’t clear why you did that. However, I don’t see how this change could cause any problems since a StructuredDataMessage is a MapMessage. 2. The second chang

Re: [VOTE] Release Log4j 2.9.0-rc1

2017-08-27 Thread Gary Gregory
On Sun, Aug 27, 2017 at 8:12 AM, Gary Gregory wrote: > From src zip file and using guidance from BUILDING.md > > ASC, MD5, SHA1, OK. > > RAT check OK > > mvn clean install OK > > CLIRR check OK but MUST be done AFTER the above and I get: > > [INFO] --- clirr-maven-plugin:2.8:check (default-cli) @

Re: [VOTE] Release Log4j 2.9.0-rc1

2017-08-27 Thread Gary Gregory
On Sun, Aug 27, 2017 at 8:12 AM, Gary Gregory wrote: > From src zip file and using guidance from BUILDING.md > > ASC, MD5, SHA1, OK. > FYI: I was able to validate against a KEYS file I imported previously. Gary > > RAT check OK > > mvn clean install OK > > CLIRR check OK but MUST be done AFTER

Re: [VOTE] Release Log4j 2.9.0-rc1

2017-08-27 Thread Ralph Goers
Matt added an exclude for the docker file back before the 2.8. release. I’m not sure why. Ralph > On Aug 27, 2017, at 7:50 AM, Gary Gregory wrote: > > Minor bug but not a blocker: the Dockerfile is missing from the src > distribution zip. > > Gary > > On Sat, Aug 26, 2017 at 8:45 PM, Ralph G

Re: [VOTE] Release Log4j 2.9.0-rc1

2017-08-27 Thread Gary Gregory
Minor bug but not a blocker: the Dockerfile is missing from the src distribution zip. Gary On Sat, Aug 26, 2017 at 8:45 PM, Ralph Goers wrote: > This is a vote to release Log4j 2.9.0 the next version of the Log4j 2 > project. > > Please download, test, and cast your votes on the log4j developer

Re: [VOTE] Release Log4j 2.9.0-rc1

2017-08-27 Thread Gary Gregory
>From src zip file and using guidance from BUILDING.md ASC, MD5, SHA1, OK. RAT check OK mvn clean install OK CLIRR check OK but MUST be done AFTER the above and I get: [INFO] --- clirr-maven-plugin:2.8:check (default-cli) @ log4j-api --- [INFO] artifact org.apache.logging.log4j:log4j-api: chec

Re: [VOTE] Release Log4j 2.9.0-rc1

2017-08-27 Thread Gary Gregory
Link to KEYS file please? Gary On Sat, Aug 26, 2017 at 8:45 PM, Ralph Goers wrote: > This is a vote to release Log4j 2.9.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 releas