Re: org.apache.logging.log4j.core.config.Configurator.initialize(String, String)

;remko.po...@gmail.com> wrote: > > I can see both sides of the argument. > > Rather than changing the semantics of the existing method, what about > adding a method `Configurator.initializeStrict(String, String)` which > fails if the specified file doesn't exist? Not sure what the best

org.apache.logging.log4j.core.config.Configurator.initialize(String, String)

Hi All: Using 2.8.2, I call org.apache.logging.log4j.core.config.Configurator.initialize(String, String) with a non-exiting file location. The method does not return null because it found another log4j2.xml file on my classpath. So I get a LoggerContext but not what I expect... That does not

[jira] [Updated] (LOG4J2-1879) Update JAnsi from 1.14 to 1.15

[ https://issues.apache.org/jira/browse/LOG4J2-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1879: - Summary: Update JAnsi from 1.14 to 1.15 (was: Update Jansi from 1.14 to 1.15) > Update JA

[jira] [Updated] (LOG4J2-1879) Update JAnsi from 1.14 to 1.15

[ https://issues.apache.org/jira/browse/LOG4J2-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1879: - Description: Update JAnsi from 1.14 to 1.15 (was: Update Jansi from 1.14 to 1.15) > Upd

[jira] [Closed] (LOG4J2-1879) Update JAnsi from 1.14 to 1.15

[ https://issues.apache.org/jira/browse/LOG4J2-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1879. Resolution: Fixed Fix Version/s: 2.9 In Git master. > Update JAnsi from 1.14 to 1

[jira] [Created] (LOG4J2-1879) Update Jansi from 1.14 to 1.15

Gary Gregory created LOG4J2-1879: Summary: Update Jansi from 1.14 to 1.15 Key: LOG4J2-1879 URL: https://issues.apache.org/jira/browse/LOG4J2-1879 Project: Log4j 2 Issue Type: Improvement

Wiki still mainly features 1.2

Hi All, This site could use a dust up: https://wiki.apache.org/logging-log4j Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition

Re: [14/14] logging-log4j2 git commit: Update BOM

Is this where a Chainsaw refresh would live? Gary On Apr 10, 2017 9:01 AM, "Ralph Goers" wrote: > I’m fine with that. I just don’t want more modules in the main project. > > Ralph > > On Apr 10, 2017, at 8:56 AM, Mikael Ståldal > wrote: >

[jira] [Commented] (LOG4J2-1873) Implement UTF-8 encoding that doesn't use CharsetEncoder

[ https://issues.apache.org/jira/browse/LOG4J2-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963050#comment-15963050 ] Gary Gregory commented on LOG4J2-1873: -- ICU4J might have something we can optionally depend

[jira] [Commented] (LOG4J2-1864) Support capped collection for MongoDB Log-Provider

[ https://issues.apache.org/jira/browse/LOG4J2-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963043#comment-15963043 ] Gary Gregory commented on LOG4J2-1864: -- The old factory method does not come into play if you remove

[jira] [Closed] (LOG4J2-1872) Update JavaMail from 1.5.5 to 1.5.6

[ https://issues.apache.org/jira/browse/LOG4J2-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1872. Resolution: Fixed Fix Version/s: 2.9 In Git master. > Update JavaMail from 1.5.5 to 1.

[jira] [Closed] (LOG4J2-1869) Update Kafka client from 0.10.1.1 to 0.10.2.0

[ https://issues.apache.org/jira/browse/LOG4J2-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1869. Resolution: Fixed Fix Version/s: 2.9 Marking for 2.9. > Update Kafka client from 0.10.

[jira] [Reopened] (LOG4J2-1869) Update Kafka client from 0.10.1.1 to 0.10.2.0

[ https://issues.apache.org/jira/browse/LOG4J2-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1869: -- > Update Kafka client from 0.10.1.1 to 0.10.

[jira] [Created] (LOG4J2-1872) Update JavaMail from 1.5.5 to 1.5.6

Gary Gregory created LOG4J2-1872: Summary: Update JavaMail from 1.5.5 to 1.5.6 Key: LOG4J2-1872 URL: https://issues.apache.org/jira/browse/LOG4J2-1872 Project: Log4j 2 Issue Type: Bug

[jira] [Closed] (LOG4J2-1869) Update Kafka client from 0.10.1.1 to 0.10.2.0

[ https://issues.apache.org/jira/browse/LOG4J2-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1869. Resolution: Fixed Assignee: Gary Gregory In Git master. > Update Kafka client from 0.10.

Re: Jenkins and Maven 3.5.0

I was thinking of just using 3.5.0. Gary On Apr 9, 2017 6:48 AM, "Apache" wrote: > Why? There is no reason our build process has to support every maven > release. > > Sent from my iPad > > On Apr 8, 2017, at 5:44 PM, Matt Sicker wrote: > > Now

Re: Jenkins and Maven 3.5.0

Sure, why not? Let's eat our own Apache dog food. Fresh too! Gary On Apr 8, 2017 5:44 PM, "Matt Sicker" wrote: > Now that Maven 3.5.0 is out, whenever Infra adds it to Jenkins, would it > make sense to switch to it there? I know in theory everything seems to work > with any

[jira] [Created] (LOG4J2-1869) Update Kafka client from 0.10.1.1 to 0.10.2.0

Gary Gregory created LOG4J2-1869: Summary: Update Kafka client from 0.10.1.1 to 0.10.2.0 Key: LOG4J2-1869 URL: https://issues.apache.org/jira/browse/LOG4J2-1869 Project: Log4j 2 Issue Type

[jira] [Created] (LOG4J2-1868) Update ZeroMQ's JeroMQ from 0.3.6 to 0.4.0

Gary Gregory created LOG4J2-1868: Summary: Update ZeroMQ's JeroMQ from 0.3.6 to 0.4.0 Key: LOG4J2-1868 URL: https://issues.apache.org/jira/browse/LOG4J2-1868 Project: Log4j 2 Issue Type

Fwd: Build failed in Jenkins: Log4jWindows » Windows,JDK 1.8 (unlimited security) 64-bit Windows only #51

Note that I ran a full build before this commit (mvn clean install) and it worked. Gary -- Forwarded message -- From: Apache Jenkins Server Date: Fri, Apr 7, 2017 at 5:08 PM Subject: Build failed in Jenkins: Log4jWindows » Windows,JDK 1.8 (unlimited

Re: Weird compilation error

> > On 7 April 2017 at 15:48, Gary Gregory <garydgreg...@gmail.com> wrote: > >> Hm, >> >> I had changed active mq testing from 5.14.1 to 5.14.4 and that yields: >> >> [ERROR] error: error reading C:\Users\ggregory\.m2\reposito >> ry\org\apach

Re: Weird compilation error

\repository\org\apache\activemq\activemq-client\5.14.4\activemq-client-5.14.4.jar; invalid LOC header (bad signature) and later the problems I initially showed. Odd! Gary On Fri, Apr 7, 2017 at 1:41 PM, Gary Gregory <garydgreg...@gmail.com> wrote: > I added to log4

Re: Weird compilation error

APSHOT (C:\vcs\git\apache\logging\logging-log4j2\log4j-bom\pom.xml) points at org.apache.logging.log4j:log4j instead of org.apache.logging:logging-parent, please verify your project structure @ line 19, column 11 @ Gary On Fri, Apr 7, 2017 at 1:34 PM, Gary Gregory <garydgreg...@gmai

Re: Weird compilation error

This is with Maven 3.3.9 though. Gary On Fri, Apr 7, 2017 at 1:11 PM, Matt Sicker <boa...@gmail.com> wrote: > Does it have a dependency on log4j-core:test? It should. Could be a bug in > your beta version of Maven ;) > > On 7 April 2017 at 14:46, Gary Gregory <garydgre

Weird compilation error

Hi All: I'm seeing this in master: [INFO] --- maven-bundle-plugin:3.2.0:manifest (default) @ log4j-1.2-api --- [INFO] [INFO] --- maven-resources-plugin:3.0.1:testResources (default-testResources) @ log4j-1.2-api --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 71

Re: Yet another logging facade

A quick review of the document appears to have SLF4J as a requirement. Shame about that. Gary On Thu, Apr 6, 2017 at 5:34 PM, Ralph Goers wrote: > Where does one comment on these? > > The problem is that they mention Java 8 support, but SLF4J doesn’t take >

[jira] [Commented] (LOG4J2-1866) Add default value to MdcPatternConverter

[ https://issues.apache.org/jira/browse/LOG4J2-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15959186#comment-15959186 ] Gary Gregory commented on LOG4J2-1866: -- Patches with unit tests are welcome :-) > Add default va

Re: MessageLayout

of the event > in the final repository so you need to make sure your events include a > unique key that can be used to remove duplicates. > > Ralph > > On Apr 3, 2017, at 8:40 PM, Gary Gregory <garydgreg...@gmail.com> wrote: > > Thanks Matt. With the Flume appender, do I

Re: MessageLayout

ut on docker containers, but I'm not the one who set >> all that up. Either way, the most reliable way to log things outside of >> files is Flume. >> >> On 3 April 2017 at 19:45, Gary Gregory <garydgreg...@gmail.com> wrote: >> >>> Wait a sec. A JMS prov

Re: MessageLayout

“%m%ex{none}”? > > How can you do auditing with the async logger? You may lose events with > that. > > Your use case is exactly why I wrote the FlumeAppender. It is very much > like JMS but a whole lot faster and guarantees events aren’t lost. > > Ralph > > On Apr 3,

Re: MessageLayout

async logger as well. No need to deal with the JMS API. Gary On Mon, Apr 3, 2017 at 4:07 PM, Remko Popma <remko.po...@gmail.com> wrote: > So, exceptions are swallowed and no newlines are rendered? Interesting. > What's the use case? > > Sent from my iPhone > > On Apr 4, 201

MessageLayout

Hi All, I am considering a new layout called "MessageLayout" which would be synonymous with:. Thoughts? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition

Re: Deep Dive into Java 9’s Stack-Walking API

ll be merging it back into the LOG4J2-1359 branch > and looking for a code review. In the meantime you are free to look at the > java9NoMultiRelease branch. > > Ralph > > > On Apr 2, 2017, at 10:03 PM, Gary Gregory <garydgreg...@gmail.com> wrote: > > FYI: https:

Deep Dive into Java 9’s Stack-Walking API

FYI: https://www.sitepoint.com/deep-dive-into-java-9s-stack-walking-api/ Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition

Re: [VOTE] Release Log4j 2.8.2 rc1

... and thank you Matt for picking up RM duty this time around. I look forward to getting 2.8.2 out the door and seeing what we have in store for 2.9! Gary On Sun, Apr 2, 2017 at 2:08 PM, Matt Sicker wrote: > This is a vote to release Log4j 2.8.2. Please download, test, and

Re: [VOTE] Release Log4j 2.8.2 rc1

+1 MD5, SHA1, ASC OK. Following BUILDING.md: RAT check OK CLIRR check on API OK mvn clean install OK CLIRR check on 1.2 API OK mvn site OK but with some Javadoc warnings: [WARNING] C:\temp\rc\apache-log4j-2.8.2-src\log4j-api\src\main\java\ org\apache\logging\log4j\ThreadContext.java:49:

Re: Upcoming release planning

Go for it :-) Gary On Mar 31, 2017 8:19 AM, "Matt Sicker" wrote: > I'd like to see two releases happen soon: > > log4j-api-scala v11: let's get this out the door soon > log4j-core 2.8.2: we have bugfixes ready and I'd also like to see a > release of this before we move on to

[jira] [Closed] (LOG4J2-1856) Update Jackson from 2.8.6 to 2.8.7.

[ https://issues.apache.org/jira/browse/LOG4J2-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1856. Resolution: Fixed Fix Version/s: 2.8.2 In Git master. > Update Jackson from 2.8.6 to 2.

[jira] [Created] (LOG4J2-1856) Update Jackson from 2.8.6 to 2.8.7.

Gary Gregory created LOG4J2-1856: Summary: Update Jackson from 2.8.6 to 2.8.7. Key: LOG4J2-1856 URL: https://issues.apache.org/jira/browse/LOG4J2-1856 Project: Log4j 2 Issue Type

[jira] [Commented] (LOG4J2-1071) Allow for bufferSize=0 in SMTP appender

[ https://issues.apache.org/jira/browse/LOG4J2-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15942130#comment-15942130 ] Gary Gregory commented on LOG4J2-1071: -- Patches welcome :-) > Allow for bufferSize=0 in S

[jira] [Resolved] (LOG4J2-1853) The default value of RandomAccessFileAppender.Builder append field is wrong

[ https://issues.apache.org/jira/browse/LOG4J2-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1853. -- Resolution: Fixed Fix Version/s: 2.8.2 Closes #66. Please verify and close this Jira

Re: org.apache.logging.log4j.ThreadContext.pop()

terface update. > Bleh, I forgot about that part. I do not think there is a better name. Gary > > On 5 March 2017 at 20:11, Gary Gregory <garydgreg...@gmail.com> wrote: > >> IIRC this is just old code mindlessly ported from log4j 1. >> >> Gary >> >>

[jira] [Commented] (LOG4J2-1753) java.lang.ClassNotFoundException: org.apache.logging.log4j.core.util.ExecutorServices when running the OSGi tests

[ https://issues.apache.org/jira/browse/LOG4J2-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900861#comment-15900861 ] Gary Gregory commented on LOG4J2-1753: -- [~jvz] The tests pass now so that solves the reported issue

Re: [VOTE] Combine the project user and dev mailing lists into user@ and dev@

On Mar 8, 2017 5:28 AM, "Matt Sicker" wrote: I may be missing some mailing lists considering I just subscribed to half of them less than five minutes ago. This is a vote to merge the various Apache Logging Services mailing lists. The proposal is to combine them as follows:

[jira] [Closed] (LOG4J2-1804) Rolling file %i based rolling broken in 2.8

[ https://issues.apache.org/jira/browse/LOG4J2-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1804. Closing as fixed in 2.8.1. > Rolling file %i based rolling broken in

Re: org.apache.logging.log4j.ThreadContext.pop()

nt). On 5 March 2017 at 09:52, Gary Gregory <garydgreg...@gmail.com> wrote: > When I want to pop the ThreadContext more than once I do: > > ThreadContext.pop(); > ThreadContext.pop(); > ThreadContext.pop(); > ThreadContext.pop(); > > Instead I'd like to update some le

org.apache.logging.log4j.ThreadContext.pop()

When I want to pop the ThreadContext more than once I do: ThreadContext.pop(); ThreadContext.pop(); ThreadContext.pop(); ThreadContext.pop(); Instead I'd like to update some legacy code to: ThreadContext.pop(4); (I know, I know, I should update that old code to push()/clear()) Thoughts on

Re: Performance page for next release.

I think we should keep the current doc pages on the site perhaps under a different heading. This would be interesting for people who cannot keep up with the latest. Gary On Fri, Mar 3, 2017 at 1:20 PM, Remko Popma wrote: > Yes but only the JMH benchmarks. Is that

[jira] [Commented] (LOG4J2-1834) Handle when LogEvent.getLoggerName() returns null properly

[ https://issues.apache.org/jira/browse/LOG4J2-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894007#comment-15894007 ] Gary Gregory commented on LOG4J2-1834: -- Not sure, the Javadoc for the method says {{null

[jira] [Commented] (LOG4J2-1820) Log4j 2.8 can lose exceptions when a security manager is present

[ https://issues.apache.org/jira/browse/LOG4J2-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891505#comment-15891505 ] Gary Gregory commented on LOG4J2-1820: -- The bottom line is that we use GitHub as a read-only mirror

[jira] [Commented] (LOG4J2-1820) Log4j 2.8 can lose exceptions when a security manager is present

[ https://issues.apache.org/jira/browse/LOG4J2-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891172#comment-15891172 ] Gary Gregory commented on LOG4J2-1820: -- Yes, I just got the patch from the URL, copied

[jira] [Resolved] (LOG4J2-1820) Log4j 2.8 can lose exceptions when a security manager is present

[ https://issues.apache.org/jira/browse/LOG4J2-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1820. -- Resolution: Fixed Assignee: Gary Gregory Fix Version/s: 2.8.2 Please verify

Re: [VOTE] Release Log4j 2.8.1-rc1

I land at AMS on March 5 9 AM. Almost! Gary On Tue, Feb 28, 2017 at 11:28 PM, Remko Popma <remko.po...@gmail.com> wrote: > > > On Wed, Mar 1, 2017 at 4:07 AM, Gary Gregory <garydgreg...@gmail.com> > wrote: > >> How long are you in Amsterdam? I might be in D

[jira] [Commented] (LOG4J2-1831) NullPointerException in HtmlLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890872#comment-15890872 ] Gary Gregory commented on LOG4J2-1831: -- I can see the problem and it's simple to fix. There might

[jira] [Resolved] (LOG4J2-1831) NullPointerException in HtmlLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1831. -- Resolution: Fixed Assignee: Gary Gregory Fix Version/s: 2.8.2 Please verify

Re: [VOTE] Release Log4j 2.8.1-rc1

+1 >From src zip distribution: ASC, MD4, SHA1 OK. Following BUILDING.md. RAT check OK. CLIRR check OK on log4j-api. FAILS: mvn clean install PASSES: mvn clean install -pl !log4j-nosql (this is a known issue) PASSES: mvn site Using Apache Maven 3.3.9

Re: [VOTE] Release Log4j 2.8.1-rc1

How long are you in Amsterdam? I might be in Dordrecht (1 hour by train IIRC) next week for work. Gary On Mon, Feb 27, 2017 at 11:36 PM, Remko Popma wrote: > FYI I won't be able to start reviewing until Wednesday (likely evening > Amsterdam time). > > On Mon, Feb 27,

[jira] [Commented] (LOG4J2-1828) add support for prudent mode in Log4j 2

[ https://issues.apache.org/jira/browse/LOG4J2-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888682#comment-15888682 ] Gary Gregory commented on LOG4J2-1828: -- Is this just having a "lock" mode on/off? >

[jira] [Commented] (LOG4J2-1807) [core] Add and implement LogEvent.toImmutable()

[ https://issues.apache.org/jira/browse/LOG4J2-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884304#comment-15884304 ] Gary Gregory commented on LOG4J2-1807: -- Sounds reasonable. > [core] Add and implem

Re: Undeprecating MessageSupplier

Makes sense. We should make we Javadoc all that. On Feb 24, 2017 10:07 AM, "Matt Sicker" wrote: > In log4j-api, the interface MessageSupplier has been deprecated ever since > we realized that we didn't need it and could just use Supplier for > lambda support. However, now that

[jira] [Commented] (LOG4J2-1820) Log4j 2.8 can lose exceptions when a security manager is present

[ https://issues.apache.org/jira/browse/LOG4J2-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883407#comment-15883407 ] Gary Gregory commented on LOG4J2-1820: -- When I apply the patch I get this failure: Tests in error

Re: Roadmap for 2.8.1

I think we can do 2.8.1 with our current bug fixes. Moving modules around feels like a 2.9 item to me but that's just me. I really like the idea of making bug fixes available ASAP. The only issue I see that fixing now is the null classloader issue for which we have a patch but it does not work for

[jira] [Commented] (LOG4J2-1820) Log4j 2.8 can lose exceptions when a security manager is present

[ https://issues.apache.org/jira/browse/LOG4J2-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879767#comment-15879767 ] Gary Gregory commented on LOG4J2-1820: -- [~jvz]: Do you feel we have consensus that [~jasontedor]'s

[jira] [Commented] (LOG4J2-1820) Log4j 2.8 can lose exceptions when a security manager is present

[ https://issues.apache.org/jira/browse/LOG4J2-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877459#comment-15877459 ] Gary Gregory commented on LOG4J2-1820: -- More generally, how can we parameterize the unit tests

[jira] [Commented] (LOG4J2-1820) Log4j 2.8 can lose exceptions when a security manager is present

[ https://issues.apache.org/jira/browse/LOG4J2-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877457#comment-15877457 ] Gary Gregory commented on LOG4J2-1820: -- Hi All, It seems that we do not need to worry about cases

[jira] [Commented] (LOG4J2-1820) Log4j 2.8 can lose exceptions when a security manager is present

[ https://issues.apache.org/jira/browse/LOG4J2-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877426#comment-15877426 ] Gary Gregory commented on LOG4J2-1820: -- What about the other 31 call sites we have

[jira] [Comment Edited] (LOG4J2-1820) Log4j 2.8 can lose exceptions when a security manager is present

[ https://issues.apache.org/jira/browse/LOG4J2-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877426#comment-15877426 ] Gary Gregory edited comment on LOG4J2-1820 at 2/22/17 3:53 AM: --- What about

[jira] [Commented] (LOG4J2-1820) Log4j 2.8 can lose exceptions when a security manager is present

[ https://issues.apache.org/jira/browse/LOG4J2-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877130#comment-15877130 ] Gary Gregory commented on LOG4J2-1820: -- I'll try to take a look tonight, Does a full build pass

[jira] [Commented] (LOG4J2-548) Log4j 2.0 with JBoss EAP 6.2

[ https://issues.apache.org/jira/browse/LOG4J2-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872725#comment-15872725 ] Gary Gregory commented on LOG4J2-548: - Thank you for your patch Eric. Did you try a full build

[jira] [Commented] (LOG4J2-1807) [core] Add and implement LogEvent.toImmutable()

[ https://issues.apache.org/jira/browse/LOG4J2-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872252#comment-15872252 ] Gary Gregory commented on LOG4J2-1807: -- I agree that it is not perfect. What do you suggest

[jira] [Closed] (LOG4J2-1819) Update Jackson from 2.8.5 to 2.8.6

[ https://issues.apache.org/jira/browse/LOG4J2-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1819. Resolution: Fixed In Git master. > Update Jackson from 2.8.5 to 2.

[jira] [Reopened] (LOG4J2-1819) Update Jackson from 2.8.5 to 2.8.6

[ https://issues.apache.org/jira/browse/LOG4J2-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1819: -- > Update Jackson from 2.8.5 to 2.8.6 > -- > >

[jira] [Updated] (LOG4J2-1819) Update Jackson from 2.8.5 to 2.8.6

[ https://issues.apache.org/jira/browse/LOG4J2-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1819: - Affects Version/s: (was: 2.7) 2.8 > Update Jackson from 2.

[jira] [Closed] (LOG4J2-1819) Update Jackson from 2.8.5 to 2.8.6

[ https://issues.apache.org/jira/browse/LOG4J2-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1819. Resolution: Fixed Fix Version/s: 2.8.1 > Update Jackson from 2.8.5 to 2.

[jira] [Created] (LOG4J2-1819) Update Jackson from 2.8.5 to 2.8.6

Gary Gregory created LOG4J2-1819: Summary: Update Jackson from 2.8.5 to 2.8.6 Key: LOG4J2-1819 URL: https://issues.apache.org/jira/browse/LOG4J2-1819 Project: Log4j 2 Issue Type: Improvement

[jira] [Resolved] (LOG4J2-1807) [core] Add and implement LogEvent.toImmutable()

[ https://issues.apache.org/jira/browse/LOG4J2-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1807. -- Resolution: Fixed In git master. [~rem...@yahoo.com], would you care to review? Gary

[jira] [Updated] (LOG4J2-1807) [core] Add and implement LogEvent.toImmutable()

[ https://issues.apache.org/jira/browse/LOG4J2-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1807: - Affects Version/s: 2.8.1 > [core] Add and implement LogEvent.toImmuta

[jira] [Resolved] (LOG4J2-1818) Fix rollover to work when filePattern contains no directory components

[ https://issues.apache.org/jira/browse/LOG4J2-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1818. -- Resolution: Fixed Fix Version/s: 2.8.1 Fixed in Git master. > Fix rollover to w

[jira] [Created] (LOG4J2-1818) Fix rollover to work when filePattern contains no directory components

Gary Gregory created LOG4J2-1818: Summary: Fix rollover to work when filePattern contains no directory components Key: LOG4J2-1818 URL: https://issues.apache.org/jira/browse/LOG4J2-1818 Project

Re: RollingAppenderSizeTest failures

equiring a running Mongo, and the Cassandra test >> works similarly although it starts up Cassandra within the JVM for you. >> >> On 3 February 2017 at 13:10, Gary Gregory <garydgreg...@gmail.com> wrote: >> >>> And if

Re: RollingAppenderSizeTest failures

OK, the rolling test is fixed. Now, the OSGi module does not build. Gary On Tue, Feb 14, 2017 at 5:08 PM, Remko Popma <remko.po...@gmail.com> wrote: > The new test failure (can't open zip) looks like a one-off... > > Sent from my iPhone > > On Feb 15, 2017, at 9:58, Ga

Re: RollingAppenderSizeTest failures

e issue was as simple as that. Gary > > Ralph > > On Feb 14, 2017, at 2:56 PM, Gary Gregory <garydgreg...@gmail.com> wrote: > > Was the problem before that threads where not finishing normally on test > completion? Could this be the same kind of issue? > > Gary

Re: RollingAppenderSizeTest failures

sers\Ralph%20Goers\.m2\repository\com\google\code\ > java-allocation-instrumenter\java-allocation-instrumenter\ > 3.0.1\java-allocation-instrumenter-3.0.1.jar]> > > Ralph > > On Feb 13, 2017, at 12:13 PM, Apache <ralph.go...@dslextreme.com> wrote: > > No. I plan to fi

[jira] [Commented] (LOG4J2-1814) Wrapper Generate$ExtendedLogger name inconvenient on Linux

[ https://issues.apache.org/jira/browse/LOG4J2-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15865090#comment-15865090 ] Gary Gregory commented on LOG4J2-1814: -- Can we just cut to the chase and give the class a decent

Re: RollingAppenderSizeTest failures

My hope was that Ralph would revert his commit that broke the build on Windows. Gary On Mon, Feb 13, 2017 at 10:01 AM, Gary Gregory <garydgreg...@gmail.com> wrote: > Maven just works as in on Windows. I have the Maven bin folder on my PATH, > that's it, it contains mvn.cmd. > &g

Re: RollingAppenderSizeTest failures

experienced with development in such an environment these days. > If you can figure out how to get the mvnw.cmd script to work in Windows, > that'd be great. > > On 13 February 2017 at 11:26, Gary Gregory <garydgreg...@gmail.com> wrote: > >> Thank you for setting that up Matt.

Re: RollingAppenderSizeTest failures

basic test matrix for Java 7 and 8 on Linux and Windows >>>>> here: <https://builds.apache.org/job/Log4j/> >>>>> >>>>> Let's see how this works. >>>>> >>>>> On 12 February 2017 at 22:40, Matt Sicker <boa...@gmail.com&

[jira] [Commented] (LOG4J2-1813) Provide shorter and more intuitive way to switch on Log4j internal debug logging

[ https://issues.apache.org/jira/browse/LOG4J2-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15863148#comment-15863148 ] Gary Gregory commented on LOG4J2-1813: -- Yeah, the "EBUG" is not pretty. I had a ques

Re: RollingAppenderSizeTest failures

Any chance building on Windows gets solved soon-ish? Gary On Thu, Feb 2, 2017 at 6:05 PM, Gary Gregory <garydgreg...@gmail.com> wrote: > Git bisec says: > > *a0f4f4db5e8e88e56eaa148d81c2ba91df606e2a is the first bad commit* > commit a0f4f4db5e8e88e56eaa148d81c2ba91df606e2a >

Re: Remko travel plans

NL is great. Enjoy! Gary On Feb 12, 2017 6:31 AM, "Remko Popma" wrote: > I will be travelling to Holland between Feb 15 and March 5th, with > sporadic internet access at times, so I may be slow to reply during this > period. > > Remko >

Re: Regarding Checkstyle, PMD, and formatting

r parens. It makes maintenance so much easier. You write the code once, and it is read forever more. Might as well make your *intentions* be crystal clear. Gary > > Ralph > > On Feb 10, 2017, at 11:32 AM, Gary Gregory <garydgreg...@gmail.com> wrote: > > On Fri, Feb 10, 2017 at 8:0

Re: Regarding Checkstyle, PMD, and formatting

0 February 2017 at 05:34, Remko Popma <remko.po...@gmail.com> wrote: >>> >>>> Generally agree except that we agreed that the final qualifier was >>>> optional. This may not be easy (or possible?) to verify automatically >>>> anyway. >

Re: Regarding Checkstyle, PMD, and formatting

s may not be easy (or possible?) to verify automatically >> anyway. >> >> Otherwise all looks reasonable. >> >> Sent from my iPhone >> >> On Feb 10, 2017, at 17:55, Mikael Ståldal <mikael.stal...@magine.com> >> wrote: >> >>

Re: Regarding Checkstyle, PMD, and formatting

t;> anyway. >> >> Otherwise all looks reasonable. >> >> Sent from my iPhone >> >> On Feb 10, 2017, at 17:55, Mikael Ståldal <mikael.stal...@magine.com> >> wrote: >> >> Seems reasonable. >> >> On Fri, Feb 10, 2017 at 5:56 AM, Gary G

Re: Regarding Checkstyle, PMD, and formatting

I agree with all that! :-) Gary On Feb 9, 2017 7:05 PM, "Matt Sicker" wrote: I was browsing through the site and took a look at the component reports. Checkstyle alone seems close to pointless as there are over 200 errors in log4j-api alone. log4j-core has over 2000 errors.

Re: Making copies of LogEvent to avoid no-GC problems

; Sent from my iPhone > > On Jan 27, 2017, at 3:32, Gary Gregory <garydgreg...@gmail.com> wrote: > > Hi All: > > Just like in our SMTP appender, I have a custom Appender which needs to > track LogEvents. To do this without falling prey to all of our no-GC epic > clevernes

Re: Logback performance improvements

If you want, I can run tests on Windows once the build works on Windows again. Let me know what args/command line... Gary On Feb 5, 2017 11:58 AM, "Apache" wrote: > I guess my MacBook Pro must fit in the Slow CPU/Fast Hard drive category. > With Logback 1.10 and -t

[jira] [Commented] (LOG4J2-1809) Add global configuration environment SPI

[ https://issues.apache.org/jira/browse/LOG4J2-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853316#comment-15853316 ] Gary Gregory commented on LOG4J2-1809: -- It seems we are entering Apache Commons Configuration

Re: RollingAppenderSizeTest failures

ows Server > used for big data clusters in the first place, so I suppose it's possible. > > On 3 February 2017 at 16:23, Gary Gregory <garydgreg...@gmail.com> wrote: > >> I hope running Cassandra on Windows is not a problem. I seems like a >> normal set up: https://www.data

Re: RollingAppenderSizeTest failures

er tested that integration test in Windows, so > perhaps it's platform-specific? Anyways, the equivalent Mongo integration > test is @Ignore'd due to requiring a running Mongo, and the Cassandra test > works similarly although it starts up Cassandra within the JVM for you. > > On 3 February 201

  1   2   3   4   5   6   7   8   9   10   >