Re: Json Template Layout

congrats! On Tue, May 26, 2020 at 5:45 AM Volkan Yazıcı wrote: > BAM! JsonTemplateLayout is merged to master! 🎉🍾 (I needed to wait > some for the GitHub write access to get sync'ed with Apache LDAP.) > > On Mon, May 25, 2020 at 9:46 PM Volkan Yazıcı > wrote: > > > > I had missed the GitBox Acco

Re: Json Template Layout

Hooray! Looks like we do have some docs to update now. On Mon, 25 May 2020 at 17:21, Ralph Goers wrote: > Congrats! > > Just a reminder - you now have write access to all the logging > repositories at GitHub. You are welcome to participate in all of them. > There are a few that could use more pa

Re: Json Template Layout

Congrats! Just a reminder - you now have write access to all the logging repositories at GitHub. You are welcome to participate in all of them. There are a few that could use more participation. Ralph > On May 25, 2020, at 1:45 PM, Volkan Yazıcı wrote: > > BAM! JsonTemplateLayout is merged

Re: Json Template Layout

BAM! JsonTemplateLayout is merged to master! 🎉🍾 (I needed to wait some for the GitHub write access to get sync'ed with Apache LDAP.) On Mon, May 25, 2020 at 9:46 PM Volkan Yazıcı wrote: > > I had missed the GitBox Account Linking Matt has mentioned. I have > just completed it and get acknowledged

Re: Json Template Layout

I had missed the GitBox Account Linking Matt has mentioned. I have just completed it and get acknowledged that I "will" have right access to the logging-* repositories. I don't know if it is a timing issue, but I still cannot see any "merge" buttons available. I will keep on refreshing the page. If

Re: [CVE-2018-1285] XXE vulnerability in Apache log4net

The fix has been committed for some time now and is available with all branches that I know. You are affected by this CVE if your application consumes configuration files from untrusted sources, especially in dtd statements. 1. You should assert that your deployment does not rely on dtd processing

Build failed in Jenkins: logging-log4net » PR-60 #1

See Changes: -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Loading trusted files from base branch master at 644cfa1ba879fb41f

Re: [CVE-2018-1285] XXE vulnerability in Apache log4net

The project page says: As of April 1, 2020 Log4Net is a dormant project of Apache Logging Services. The dormant status means the project has been classified as inactive since it has had no recent development activity and there are no active volunteers to perform code reviews, commit code, or perfo

Re: JsonTemplateLayout template directives

While the first syntax is shorter, I actually like the second syntax better. It is clearer than all the stuff being tacked on after “json:” and it provides more room to be extended. Ralph > On May 25, 2020, at 6:00 AM, Volkan Yazıcı wrote: > > Hello, > > In JTL, we employ two templating lang

Re: Json Template Layout

I see the squash and merge button at the bottom. I just approved the PR so maybe you can see it now? If not, then the steps Matt has provided may be needed. We will need to update the new committer email to reflect this if that is required. If you are still having problems and need me to do it

[CVE-2018-1285] XXE vulnerability in Apache log4net

Hi, Good Day! Is there any mitigation or vulnerability fix available for .NET Core frameworks? Please let me know. Regards Suthish

Re: Json Template Layout

Make sure your account is linked properly: https://gitbox.apache.org/setup/ On Mon, May 25, 2020 at 07:23 Volkan Yazıcı wrote: > Ralph, I can indeed see I am a member of the Apache organization. > Though I don't see a "merge" option appearing in the PR page. Could it > be because of the "change

JsonTemplateLayout template directives

Hello, In JTL, we employ two templating languages within each other. Consider the following GelfLayout.json: { "version": "1.1", "host": "${hostName}", "short_message": "${json:message}", "full_message": "${json:exception:stackTrace:text}", "timestamp": "${json:t

Re: Json Template Layout

Ralph, I can indeed see I am a member of the Apache organization. Though I don't see a "merge" option appearing in the PR page. Could it be because of the "change request" of yours? If so, would you mind resolving that request, please? (Sorry, I don't see any other visual cue to proceed further. Ma