[jira] [Closed] (LOG4J2-427) Support YAML as configuration format

[ https://issues.apache.org/jira/browse/LOG4J2-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Reelsen closed LOG4J2-427. looks good. thanks for adding license headers... > Support YAML as configuration format >

[jira] [Closed] (LOG4J2-299) Ability to retrieve original Throwable from ThrowableProxy

[ https://issues.apache.org/jira/browse/LOG4J2-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jeremy franklin-ross closed LOG4J2-299. --- verified, thanks > Ability to retrieve original Throwable from ThrowableProxy > ---

Re: [jira] [Created] (LOG4J2-552) Logic of isInstanceOf are not consistent in log4j-api's Log4jMarker and log4j-slf4j-impl's MarkerWrapper

Similar to AbstractLogger, it would be useful to have AbstractLoggerContext and possibly AbstractMarker (at least if that helps in this bug context). Regarding LogManager, that could use some sort of context of its own so that the LoggerContextFactory itself can be dynamically replaced after the sy

Re: 2.0 release triage

I like the idea of having a 2.1 version in Jira for items I intend to address after the 2.0 release. Items without version would (to me) mean either long-term items or items that I don't have the expertise for (or interest in, grin). One thing I find different in an open source project from wor

Re: Config styles

And one of the awesome side effects of Ralph's config system is that it also makes it easy to expose different ways to specify a configuration outside of log4j-core. For instance, one of the OSGi features I'll be adding down the road are various ways to configure log4j using standard OSGi configura

Re: Config styles

On Thu, Feb 27, 2014 at 6:59 PM, Ralph Goers wrote: > First, my initial goal was to make it so that you could use the core > features of Log4j 2 with no third party dependencies. I am not sure if that > is true any more but I see no reason to introduce one for configuration. > > Second, I don’t re

Re: Config styles

First, my initial goal was to make it so that you could use the core features of Log4j 2 with no third party dependencies. I am not sure if that is true any more but I see no reason to introduce one for configuration. Second, I don’t really see what benefit we would be getting. Perhaps that is

2.0 release triage

One of the things that I find difficult right now is knowing what needs the most attention for the purpose of releasing 2.0. There are actually very few issues in JIRA that are assigned to 2.0 or 2.0-rc2. There are a daunting number of issues that are not assigned a fix version. >From what I can s

[jira] [Commented] (LOG4J2-537) application does not end.

[ https://issues.apache.org/jira/browse/LOG4J2-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13915194#comment-13915194 ] Remko Popma commented on LOG4J2-537: The reason I asked is that I'm trying to understa

Config styles

I just saw a commit for YAML config. Can we review what Simone T. did a while back in the area of configuration? @Simone: Can you give an overview? Thank you, Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition

[jira] [Updated] (LOG4J2-345) logging.log4j-1.2-api doesn't export the log4j API 1.2. Dependent bundles can not be resolved.

[ https://issues.apache.org/jira/browse/LOG4J2-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-345: --- Fix Version/s: (was: 2.0-rc1) 2.0-rc2 > logging.log4j-1.2-api doesn't export t

[jira] [Updated] (LOG4J2-160) Include option in throwable pattern converter to control stack trace separator

[ https://issues.apache.org/jira/browse/LOG4J2-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-160: --- Fix Version/s: (was: 2.0-rc1) 2.0-rc2 > Include option in throwable pattern co

[jira] [Updated] (LOG4J2-159) log4j.xml loading from classpath not working correct in osgi environment

[ https://issues.apache.org/jira/browse/LOG4J2-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-159: --- Fix Version/s: (was: 2.0-rc1) 2.0-rc2 > log4j.xml loading from classpath not w

[jira] [Updated] (LOG4J2-346) Cyclic dependency in OSGi-context. Apache Log4j SLF4J Binding <-> slf4j-api

[ https://issues.apache.org/jira/browse/LOG4J2-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-346: --- Fix Version/s: (was: 2.0-rc1) 2.0-rc2 > Cyclic dependency in OSGi-context. Apa

[jira] [Updated] (LOG4J2-508) Add new Levels: NOTICE, DIAG, VERBOSE.

[ https://issues.apache.org/jira/browse/LOG4J2-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-508: --- Fix Version/s: (was: 2.0-rc1) 2.0-rc2 > Add new Levels: NOTICE, DIAG, VERBOSE.

[jira] [Updated] (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:all-tabpanel ] Ralph Goers updated LOG4J2-548: --- Fix Version/s: (was: 2.0-rc1) 2.0-rc2 > Log4j 2.0 with JBoss EAP 6.2 > --

[jira] [Created] (LOG4J2-554) No easy way to point to a configuration file in the WEB-INF folder

Russell J. Nile created LOG4J2-554: -- Summary: No easy way to point to a configuration file in the WEB-INF folder Key: LOG4J2-554 URL: https://issues.apache.org/jira/browse/LOG4J2-554 Project: Log4j 2

[jira] [Resolved] (LOG4J2-427) Support YAML as configuration format

[ https://issues.apache.org/jira/browse/LOG4J2-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-427. Resolution: Fixed Fix Version/s: 2.0-rc2 Assignee: Ralph Goers Patch applied in rev

[jira] [Resolved] (LOG4J2-378) Logging generates file named ${sys on some systems

[ https://issues.apache.org/jira/browse/LOG4J2-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-378. Resolution: Fixed Added date and ctx to default interpolator in revision 1572722. Please verify an

[jira] [Created] (LOG4J2-553) Migration from 1.x page lists incorrect classes

Mike Calmus created LOG4J2-553: -- Summary: Migration from 1.x page lists incorrect classes Key: LOG4J2-553 URL: https://issues.apache.org/jira/browse/LOG4J2-553 Project: Log4j 2 Issue Type: Bug

[jira] [Resolved] (LOG4J2-468) Dynamically (programmatically) add logger in Log4j2

[ https://issues.apache.org/jira/browse/LOG4J2-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-468. Resolution: Fixed Assignee: Ralph Goers Fixed in revision 1572705. Please verify and close.

[jira] [Commented] (LOG4J2-537) application does not end.

[ https://issues.apache.org/jira/browse/LOG4J2-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914239#comment-13914239 ] moonumi commented on LOG4J2-537: thank to comment Remko Popma. I will test and learn log4