Re: 2.6 Release

Good stuff! This reminded me I need to take a look at my backup strategy. :-) On Sun, May 22, 2016 at 2:12 PM, Ralph Goers wrote: > I fixed the license header issues. Found a bug in how properties were > being merged into composite configurations - that was causing the problem > with ${filename}

[jira] [Commented] (LOG4J2-623) Better structure of Thread Context Map in JSONLayout

[ https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295408#comment-15295408 ] Remko Popma commented on LOG4J2-623: Just to double-check: this is not a showstopper f

Re: 2.6 Release

I fixed the license header issues. Found a bug in how properties were being merged into composite configurations - that was causing the problem with ${filename}. Now all I need is to get my personal MacBook Pro to be able to boot. Ralph > On May 21, 2016, at 5:57 PM, Remko Popma wrote: > >

[jira] [Commented] (LOG4J2-623) Better structure of Thread Context Map in JSONLayout

[ https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295351#comment-15295351 ] Gary Gregory commented on LOG4J2-623: - Don't forget that there is YAML as well. > Bet

[jira] [Commented] (LOG4J2-623) Better structure of Thread Context Map in JSONLayout

[ https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295346#comment-15295346 ] Remko Popma commented on LOG4J2-623: Since the same code is used for XML and JSON, who

Re: 2.6 Release

About the ThreadContext map in JSON/YAML format: towards the end I see a comment from Ralph that the current output is wrong. If you have the bandwidth I'd say go ahead and fix it. On Friday, 20 May 2016, Mikael Ståldal wrote: > What about the format for thread context map in JsonLayout and Yaml

Re: 2.6 Release

On Sat, May 21, 2016 at 7:17 AM, Remko Popma wrote: > Got it. No rush. Enjoy! > +1. Travel safe. Gary > Sent from my iPhone > > On 2016/05/21, at 23:02, Ralph Goers wrote: > > No. There is still one unit test generating the ${filename} file. I have > fixed the other one but have not committe

Re: 2.6 Release

Got it. No rush. Enjoy! Sent from my iPhone > On 2016/05/21, at 23:02, Ralph Goers wrote: > > No. There is still one unit test generating the ${filename} file. I have > fixed the other one but have not committed it yet. I will do that when I get > them both fixed. I am visiting with family th

Re: 2.6 Release

No. There is still one unit test generating the ${filename} file. I have fixed the other one but have not committed it yet. I will do that when I get them both fixed. I am visiting with family this morning and flying this afternoon so I don’t know how much I will get done today. Ralph > On May

Re: 2.6 Release

Are all the license header issues resolved? On Saturday, 21 May 2016, Ralph Goers wrote: > Sorry, I am still traveling. To make matters worse, my Mac that has my > code signing key won’t boot. I will be taking it to the Apple store on > Monday. I don’t see anything wrong with the hardware. I thi

Re: 2.6 Release

Sorry, I am still traveling. To make matters worse, my Mac that has my code signing key won’t boot. I will be taking it to the Apple store on Monday. I don’t see anything wrong with the hardware. I think something went wrong with the last OS/X update. So it is still going to be a few days. Ral

Re: 2.6 Release

So I'm thinking it may be better to leave in the Kafka workaround and release current master as it is. (Can't wait to get 2.6 out there, by the way!) :-) On Saturday, 21 May 2016, Remko Popma wrote: > I took a look at LOG4J2-1390 > and the ass