[jira] [Assigned] (LOG4J2-1299) Add pattern converter for thread id in PatternLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reassigned LOG4J2-1299: Assignee: Gary Gregory > Add pattern converter for thread id in PatternLayout > --

[jira] [Commented] (LOG4J2-1299) Add pattern converter for thread id in PatternLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173282#comment-15173282 ] Gary Gregory commented on LOG4J2-1299: -- Allowing for the the thread priority seems l

[jira] [Commented] (LOG4J2-1299) Add pattern converter for thread id in PatternLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173277#comment-15173277 ] Gary Gregory commented on LOG4J2-1299: -- I think I can see: - Create a org.apache.lo

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

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

[jira] [Commented] (LOG4J2-1300) Remove serializability from classes that don't need it

[ https://issues.apache.org/jira/browse/LOG4J2-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173077#comment-15173077 ] Remko Popma commented on LOG4J2-1300: - I like this much better than just making every

[jira] [Commented] (LOG4J2-1295) Automated testing to verify no temporary objects allocated in gc-free configuration

[ https://issues.apache.org/jira/browse/LOG4J2-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172963#comment-15172963 ] Matt Sicker commented on LOG4J2-1295: - One little bit of help you have here is that I

[jira] [Commented] (LOG4J2-1300) Remove serializability from classes that don't need it

[ https://issues.apache.org/jira/browse/LOG4J2-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172964#comment-15172964 ] Gary Gregory commented on LOG4J2-1300: -- Fine with me. > Remove serializability from

[jira] [Updated] (LOG4J2-1300) Remove serializability from classes that don't need it

[ https://issues.apache.org/jira/browse/LOG4J2-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1300: Description: Appenders and Filters are already supposed to be Serializable based on the abstract cl

[jira] [Updated] (LOG4J2-1300) Remove serializability from classes that don't need it

[ https://issues.apache.org/jira/browse/LOG4J2-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1300: Summary: Remove serializability from classes that don't need it (was: Make plugins consistently im

[jira] [Commented] (LOG4J2-1300) Make plugins consistently implement Serializable

[ https://issues.apache.org/jira/browse/LOG4J2-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172932#comment-15172932 ] Matt Sicker commented on LOG4J2-1300: - I'd actually like to reverse this issue by rem

[jira] [Commented] (LOG4J2-1301) Automatic reconfiguration with xml and xinclude

[ https://issues.apache.org/jira/browse/LOG4J2-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172843#comment-15172843 ] Gary Gregory commented on LOG4J2-1301: -- Yes, please provide a patch with unit tests.

[jira] [Comment Edited] (LOG4J2-1301) Automatic reconfiguration with xml and xinclude

[ https://issues.apache.org/jira/browse/LOG4J2-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172784#comment-15172784 ] Alan Achtenberg edited comment on LOG4J2-1301 at 2/29/16 10:49 PM:

[jira] [Updated] (LOG4J2-1301) Automatic reconfiguration with xml and xinclude

[ https://issues.apache.org/jira/browse/LOG4J2-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Achtenberg updated LOG4J2-1301: Attachment: MyXmlConfigurationFactory.java MyXmlConfiguration.java

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

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Jenkins build became unstable: Log4j 2.x #1738

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Re: taglib questions

Yeah me neither, it's all REST and JSON for me! On 29 February 2016 at 11:42, Gary Gregory wrote: > On Mon, Feb 29, 2016 at 9:40 AM, Matt Sicker wrote: > >> Is there a point in throwing an exception in a JSP file? >> > > No idea, I've not written a JSP in a million years! ;-) > > Gary > > >> >>

Re: taglib questions

On Mon, Feb 29, 2016 at 9:40 AM, Matt Sicker wrote: > Is there a point in throwing an exception in a JSP file? > No idea, I've not written a JSP in a million years! ;-) Gary > > As to the AllTag and OffTag, those sound useful. > > On 29 February 2016 at 11:37, Gary Gregory wrote: > >> We hav

[jira] [Commented] (LOG4J2-1301) Automatic reconfiguration with xml and xinclude

[ https://issues.apache.org/jira/browse/LOG4J2-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172209#comment-15172209 ] Gary Gregory commented on LOG4J2-1301: -- Hi [~Alan Achtenberg], Patches are, of cour

Re: taglib questions

Is there a point in throwing an exception in a JSP file? As to the AllTag and OffTag, those sound useful. On 29 February 2016 at 11:37, Gary Gregory wrote: > We have a org.apache.logging.log4j.taglib.CatchingTag but not a > ThrowingTag, is that OK? > > We do not have an AllTag or OffTag (for th

taglib questions

We have a org.apache.logging.log4j.taglib.CatchingTag but not a ThrowingTag, is that OK? We do not have an AllTag or OffTag (for the ALL and OFF levels), is that OK? Gary -- E-Mail: [email protected] | [email protected] Java Persistence with Hibernate, Second Edition

[jira] [Updated] (LOG4J2-1301) Automatic reconfiguration with xml and xinclude

[ https://issues.apache.org/jira/browse/LOG4J2-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Achtenberg updated LOG4J2-1301: Description: Automatic reconfiguration does not work with xinclude/xml. Modifying xinclude

[jira] [Closed] (LOG4J2-1289) Change flow logging text from "entry' to "Enter" and "exit" to "Exit"

[ https://issues.apache.org/jira/browse/LOG4J2-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1289. Resolution: Fixed All done. > Change flow logging text from "entry' to "Enter" and "exit" to "Exit

[jira] [Created] (LOG4J2-1301) Automatic reconfiguration with xml and xinclude

Alan Achtenberg created LOG4J2-1301: --- Summary: Automatic reconfiguration with xml and xinclude Key: LOG4J2-1301 URL: https://issues.apache.org/jira/browse/LOG4J2-1301 Project: Log4j 2 Issue

Re: Education

To be honest, I never wanted to promote the idea of people coding to the Log4j 2 API and then using something else. It is supported only because we have to. As to Gary’s point, I never wanted Logger.setLevel() because it is really requires that a LoggerConfig be created behind the scene, if it

Re: Education

Currently it might be necessary to have an abstraction API in some cases, but I don't like the idea of promoting Log4J 2 as the best logging abstraction API. We should promote Log4J 2 as the best complete logging solution for the JVM. I see the possibility to plug in a different impl into log4j-ap

Re: Education

Plus log4j-api has more features than slf4j-api out of the box without requiring additional impl support to handle. Some of these APIs could be added to slf4j-api, of course, though they're not there yet. On 29 February 2016 at 10:42, Gary Gregory wrote: > But we do provide an abstraction API, a

Re: Education

But we do provide an abstraction API, and in fact some of the design in has a bit of a LCD feel to it. For example, we do not have a Logger.setLevel() API. For good or bad, some folks DO want an abstracted logging API, and this is required to get a large stack of 3rd party components working toget

Re: Education

I think the idea of having an abstraction API for different logging implementation is inherently bad. Both commons-logging and SLF4J have probably created more problems than they have solved. One reason I like Log4J 2 is that it doesn't claim to be an abstraction API, and I see it as a way to even

Re: Education

However, it is important to remember that SLF4J was created before Logback and was meant to be a new abstraction API. You can see that right here in the archives for this mailing list. OTOH, Log4j 2’s API was created so that “normal” users would be able to know what was safe to code against a

Re: Education

Because some people think that log4j-api isn't analogous to slf4j-api where log4j-core is like logback. It's a naming confusion I'd guess. On 29 February 2016 at 03:38, Mikael Ståldal wrote: > Why is it important to point out that Log4j 2 has API / impl separation? > > On Fri, Feb 26, 2016 at 10

Re: Education

On Feb 29, 2016 1:38 AM, "Mikael Ståldal" wrote: > > Why is it important to point out that Log4j 2 has API / impl separation? Because folks think of this as a major selling point for SLF4J which Log4j 1 does not have. Gary > > On Fri, Feb 26, 2016 at 10:33 PM, Ralph Goers wrote: >> >> Not on th

Re: [1/2] logging-log4j2 git commit: [LOG4J2-1300] Make appender managers and dependencies serializable.

I added a comment to LOG4J2-1300. The main idea is that there are a lot of fake serializable classes in log4j-core, and I was working on normalizing that. On 29 February 2016 at 01:31, Ralph Goers wrote: > Why are you doing this? > > Ralph > > On Feb 28, 2016, at 10:33 PM, Matt Sicker wrote: >

Re: [2/2] logging-log4j2 git commit: [LOG4J2-1300] Make remaing StrLookups serializable.

They're contained in Serializable classes, though whether or not those containing classes should be Serializable is another story. On 29 February 2016 at 01:36, Ralph Goers wrote: > StrLookup and StrSubstitutor originated in Commons but were modified to > support log events. > > Again, who needs

[jira] [Commented] (LOG4J2-1300) Make plugins consistently implement Serializable

[ https://issues.apache.org/jira/browse/LOG4J2-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171943#comment-15171943 ] Matt Sicker commented on LOG4J2-1300: - I was thinking about this since last night, an

[jira] [Commented] (LOG4J2-1300) Make plugins consistently implement Serializable

[ https://issues.apache.org/jira/browse/LOG4J2-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171815#comment-15171815 ] Mikael Ståldal commented on LOG4J2-1300: I don't think we should make anything Se

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171730#comment-15171730 ] Joern Huxhorn commented on LOG4J2-1226: --- Any chance of getting this fixed in the ne

Re: Education

Why is it important to point out that Log4j 2 has API / impl separation? On Fri, Feb 26, 2016 at 10:33 PM, Ralph Goers wrote: > Not on that site. The issue he is bringing up was discusses a few years > ago either on one of our lists. > > Ralph > > On Feb 26, 2016, at 2:24 PM, Gary Gregory wrote