Re: [VOTE] Release Log4j Scala API version 11.0 RC2

+1 - ASC, MD5 and SHA1 are OK on src zip. - Building it worked for me from the src zip with 'mvn clean install site'. - RAT check OK. - I did not try to use build products from Scala. Using: Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T12:39:06-07:00) Maven home: C:\J

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

So we're reaching the same state as the first release candidate: 1 cast vote, 1 implicit vote (I'll wait), and still no 3rd vote. Can I get another vote? On 17 July 2017 at 10:13, Matt Sicker wrote: > Agreed. I've been using 11.0-SNAPSHOT in my projects at work for a while > now as it is. > > On

[GitHub] logging-log4j2 pull request #94: remove unnecessary/empty comment

GitHub user kpm1985 opened a pull request: https://github.com/apache/logging-log4j2/pull/94 remove unnecessary/empty comment the title says it all You can merge this pull request into a Git repository by running: $ git pull https://github.com/kpm1985/logging-log4j2 master Alte

Jenkins build is back to stable : Log4j 2.x #2920

See

[GitHub] logging-log4j2 issue #82: Add a new LuceneAppender which writes logging even...

Github user garydgregory commented on the issue: https://github.com/apache/logging-log4j2/pull/82 Can you provide any documentation for the new appender? That would help a LOT! :-) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

Re: Lilith and Log4j 2

I’ll give this a shot over the next view days. Thanks! On 19. July 2017 at 21:33:49, Mikael Ståldal (mi...@apache.org) wrote: > JsonLayout (and XmlLayout and YamlLayout) now supports 0-byte > termination of log events. Will be part of the upcoming 2.9 release. > > > On 2017-07-18 11:48, Jörn

Jenkins build is still unstable: Log4j 2.x #2919

See

Re: Lilith and Log4j 2

JsonLayout (and XmlLayout and YamlLayout) now supports 0-byte termination of log events. Will be part of the upcoming 2.9 release. On 2017-07-18 11:48, Jörn Huxhorn wrote: A general event header and footer would probably be overkill. I’m using the following interface in Lilith: public interf

[jira] [Resolved] (LOG4J2-1981) JsonLayout, XmlLayout and YamlLayout should support 0-byte termination of log events

[ https://issues.apache.org/jira/browse/LOG4J2-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1981. Resolution: Fixed Fix Version/s: 2.9 In Git master, please verify and close [~huxi].

[jira] [Updated] (LOG4J2-1981) JsonLayout, XmlLayout and YamlLayout should support 0-byte termination of log events

[ https://issues.apache.org/jira/browse/LOG4J2-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1981: --- Summary: JsonLayout, XmlLayout and YamlLayout should support 0-byte termination of log events

Jenkins build became unstable: Log4j 2.x #2918

See

[jira] [Assigned] (LOG4J2-1981) JsonLayout (and possibly XmlLayout and YamlLayout) should support 0-byte termination

[ https://issues.apache.org/jira/browse/LOG4J2-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reassigned LOG4J2-1981: -- Assignee: Mikael Ståldal > JsonLayout (and possibly XmlLayout and YamlLayout) should s

[jira] [Commented] (LOG4J2-1981) JsonLayout (and possibly XmlLayout and YamlLayout) should support 0-byte termination

[ https://issues.apache.org/jira/browse/LOG4J2-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16093605#comment-16093605 ] Mikael Ståldal commented on LOG4J2-1981: Not really. > JsonLayout (and possibly

Jenkins build is back to stable : Log4j 2.x #2917

See

Re: Opportunities for cohesion improvement and refatoring.

I think AbstractConfiguration (along with XmlConfiguration and JsonConfiguration) seems like a good candidate. I've had it on a list of mine to try to refactor one day. As Ralph said, Logger is pretty off limits being a public API (the duplication is somewhat intentional for user convenience and op

Re: Opportunities for cohesion improvement and refatoring.

Logger is the main interface for logging. I am not sure why we would want to refactor it. It is also part of the public API so any changes must be backward compatible. The LogEvent is the class that captures the logging data. It has several variations as you can see. Although it is not part of

[jira] [Commented] (LOG4J2-1421) Custom plugins packaged in jar files are not loaded by "packages" property mecanism

[ https://issues.apache.org/jira/browse/LOG4J2-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092987#comment-16092987 ] Martin Schröder commented on LOG4J2-1421: - I'm running into the same issue with t

Re: Opportunities for cohesion improvement and refatoring.

Hi, You should do atomar modifications in single commits and file one pull request for a sensible set of patches. Remember to also write sensible commit messages that explain what is done and why it is done. This allows easy and fast code reviews. Github is great for doing all but the actual codin

Opportunities for cohesion improvement and refatoring.

Hello everyone. My name is João Paulo, I am a graduate student the Federal University of Uberlandia, Brazil. I was analyzing the modularization of some classes of log4j, and I identified some opportunities for cohesion improvement in the following classes: Logger DefaultConfigurationBuilder Con

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092898#comment-16092898 ] Ajitha commented on LOG4J2-1921: I will update you in a day. > Getting ClassCastExceptio

[GitHub] logging-log4j2 issue #93: modification to resolver to discover jar assests w...

Github user ta924 commented on the issue: https://github.com/apache/logging-log4j2/pull/93 Hi. Sorry for the delay had to prep for a few presentations the last couple days. I will shoot to have one ready by the end of the week. --- If your project is set up for it, you can reply to

Re: [log4net] ci pipeline status update

I have created this INFRA ticket regarding .net-2.0, node labels and the missing .net-3.5 on windows-2012-3: https://issues.apache.org/jira/browse/INFRA-14645 2017-07-19 10:54 GMT+02:00 Dominik Psenner : > > > On 19 Jul 2017 6:35 a.m., "Stefan Bodewig" wrote: > > On 2017-07-18, Dominik Psenner

Re: [log4net] ci pipeline status update

On 19 Jul 2017 6:35 a.m., "Stefan Bodewig" wrote: On 2017-07-18, Dominik Psenner wrote: > oohh how I like to be the bringer of good news! Right now I was finally > able to fix the building of the netstandard target by providing a > jenkinsfile script that detects the UID and GID of the working p

Re: [jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

I can work about 25 hours a week on the Android branch if it would be useful. I am a student so consider the source, but I've been following and using this project to pop my open source 🍒 On Jul 19, 2017 12:00 AM, "Ralph Goers (JIRA)" wrote: > > [ https://issues.apache.org/jira/browse/LOG4

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092682#comment-16092682 ] Ralph Goers commented on LOG4J2-1921: - Gradie? We use Maven as our build tool and git