[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15671581#comment-15671581 ] Steve Cohen commented on LOG4J2-1528: - Thank you for this feature. I think it has wider applicability than you may realize. In an environment with a Servlet loading several EJBs that we want to have separate deployments and logging configurations we need a way to adjust the configuration for the master servlet webapp whenever a new EJB is deployed or undeployed. This will greatly help with this scenario. > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > Fix For: 2.7 > > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15474107#comment-15474107 ] Gary Gregory commented on LOG4J2-1528: -- Cool, thank you. > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > Fix For: 2.7 > > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15473306#comment-15473306 ] Mikael Ståldal commented on LOG4J2-1528: I changed it to two spaces for indention. > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > Fix For: 2.7 > > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15471328#comment-15471328 ] Gary Gregory commented on LOG4J2-1528: -- I get CR LF for line endings. I also get nasty TABs for indentation. Can we use spaces like we do in our sources? > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > Fix For: 2.7 > > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[
https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15470100#comment-15470100
]
Mikael Ståldal commented on LOG4J2-1528:
[~garydgregory], can you test this on Windows by running
{{org.apache.log4j.config.Log4j1ConfigurationConverter}} and verify that the
produced xml config file has correct line endings?
> Serialize configuration into a log4j2.xml file
> --
>
> Key: LOG4J2-1528
> URL: https://issues.apache.org/jira/browse/LOG4J2-1528
> Project: Log4j 2
> Issue Type: New Feature
> Components: Configurators
>Affects Versions: 2.6.2
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
> Fix For: 2.7
>
>
> This would be useful for e.g. converting from Log4j 1 to Log4j 2 config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[
https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467261#comment-15467261
]
Mikael Ståldal commented on LOG4J2-1528:
Then someone who use Windows have to change the {{EOL}} constant in
{{DefaultConfigurationBuilder}} to {{System.lineSeparator()}} and do whatever
it takes to make the unit test {{ConfigurationBuilderTest}} pass on Windows.
> Serialize configuration into a log4j2.xml file
> --
>
> Key: LOG4J2-1528
> URL: https://issues.apache.org/jira/browse/LOG4J2-1528
> Project: Log4j 2
> Issue Type: New Feature
> Components: Configurators
>Affects Versions: 2.6.2
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
> Fix For: 2.7
>
>
> This would be useful for e.g. converting from Log4j 1 to Log4j 2 config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467249#comment-15467249 ] Remko Popma commented on LOG4J2-1528: - On Windows, the generated XML config files should really use \r\n line endings, or many editors (Notepad for example) will display the text as a single line. In the test it is okay to hard code \n, but for non-test the native line ending is much preferable. > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > Fix For: 2.7 > > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466948#comment-15466948 ] Mikael Ståldal commented on LOG4J2-1528: So you think that we should produce XML config files with \r\n line endings on Windows? > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > Fix For: 2.7 > > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466935#comment-15466935 ] Gary Gregory commented on LOG4J2-1528: -- There is still something wrong. It's not critical, but it's not right. Gary > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > Fix For: 2.7 > > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466756#comment-15466756 ] Mikael Ståldal commented on LOG4J2-1528: Are we fine with producing XML config files with \n line endings on all platforms, including Windows? Maybe we can remove the "HACK!" comment in the test? > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > Fix For: 2.7 > > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15465273#comment-15465273 ] Gary Gregory commented on LOG4J2-1528: -- Yes, I hard coded EOL to be "\n" instead of System.lineSeparator in the test. Not sure that is the right thing to do... > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > Fix For: 2.7 > > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15464780#comment-15464780 ] Mikael Ståldal commented on LOG4J2-1528: [~garydgregory] did you mange to fix it? > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > Fix For: 2.7 > > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458750#comment-15458750 ] Mikael Ståldal commented on LOG4J2-1528: What magic string? > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > Fix For: 2.7 > > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458752#comment-15458752 ] Mikael Ståldal commented on LOG4J2-1528: Maybe you can help me fix this? It's hard for me without a Windows machine to test on. > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > Fix For: 2.7 > > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[
https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458661#comment-15458661
]
Gary Gregory commented on LOG4J2-1528:
--
Nope:
{noformat}
org.junit.ComparisonFailure: expected:<...' encoding='UTF-8'?>[
MyValue
]
> but was:<...' encoding='UTF-8'?>[
MyValue
]
>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at
org.apache.logging.log4j.core.config.builder.ConfigurationBuilderTest.testXmlConstructing(ConfigurationBuilderTest.java:89)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:678)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
{noformat}
Whatever the EOL is should be refactored into a variable or constant instead of
the current magic string.
> Serialize configuration into a log4j2.xml file
> --
>
> Key: LOG4J2-1528
> URL: https://issues.apache.org/jira/browse/LOG4J2-1528
> Project: Log4j 2
> Issue Type: New Feature
> Components: Configurators
>Affects Versions: 2.6.2
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
> Fix For: 2.7
>
>
> This would be useful for e.g. converting from Log4j 1 to Log4j 2 config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458520#comment-15458520 ] Mikael Ståldal commented on LOG4J2-1528: Better now? > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > Fix For: 2.7 > > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456007#comment-15456007 ] Gary Gregory commented on LOG4J2-1528: -- Crap, I edited the wrong comment with the new unit test failures. Both comments now show my latest test result which at first glance seem like the same failure. > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > Fix For: 2.7 > > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15455862#comment-15455862 ] Mikael Ståldal commented on LOG4J2-1528: Does it work better now? > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > Fix For: 2.7 > > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15443357#comment-15443357 ] Remko Popma commented on LOG4J2-1528: - I have looked at the branch. This is all new functionality and I don't see any issue. I'm fine with merging this into master. > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > Fix For: 2.7 > > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[
https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429924#comment-15429924
]
Remko Popma commented on LOG4J2-1528:
-
Looking at the code snippet, yes:
LoggerConfig looks at the {{includeLocationConfigValue}} configuration String
to see if the user actually specified a value or not. So at configuration time,
there are three values.
> Serialize configuration into a log4j2.xml file
> --
>
> Key: LOG4J2-1528
> URL: https://issues.apache.org/jira/browse/LOG4J2-1528
> Project: Log4j 2
> Issue Type: New Feature
> Components: Configurators
>Affects Versions: 2.6.2
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
> Fix For: 2.7
>
>
> This would be useful for e.g. converting from Log4j 1 to Log4j 2 config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429844#comment-15429844 ] Mikael Ståldal commented on LOG4J2-1528: I could not get that to work properly for a Configuration other than BuiltConfiguration from ConfigurationBuilder (I tried with XmlConfiguration). And then it's quite pointless, so I dropped it. > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429822#comment-15429822 ] Mikael Ståldal commented on LOG4J2-1528: I have fixed this now. > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429805#comment-15429805 ] Mikael Ståldal commented on LOG4J2-1528: OK, added test and found out that it was wrong, and fixed it. > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429796#comment-15429796 ] Ralph Goers commented on LOG4J2-1528: - Is there a test for that? If not, add one and find out! > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[
https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429774#comment-15429774
]
Mikael Ståldal commented on LOG4J2-1528:
Has anyone tried to add a CustomLevel with ConfigurationBuilder? I think it is
not implemented correctly. In {{DefaultCustomLevelComponentBuilder}}:
{code}
addAttribute("level", Integer.toString(level));
{code}
Shouldn't that be "intLevel" to be consistent with {{CustomLevelConfig}}?
> Serialize configuration into a log4j2.xml file
> --
>
> Key: LOG4J2-1528
> URL: https://issues.apache.org/jira/browse/LOG4J2-1528
> Project: Log4j 2
> Issue Type: New Feature
> Components: Configurators
>Affects Versions: 2.6.2
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
>
> This would be useful for e.g. converting from Log4j 1 to Log4j 2 config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429766#comment-15429766 ] Mikael Ståldal commented on LOG4J2-1528: So includeLocation on loggers should be considered tri-state from a configuration point of view? > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429765#comment-15429765 ] Ralph Goers commented on LOG4J2-1528: - I am pretty sure that is not true. The locarion information is lazily obtained in synchronous logging so is enabled by default. Asynchronous loggers disable it by default. > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[
https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429764#comment-15429764
]
Mikael Ståldal commented on LOG4J2-1528:
>From LoggerConfig:
{code}
// Note: for asynchronous loggers, includeLocation default is FALSE,
// for synchronous loggers, includeLocation default is TRUE.
protected static boolean includeLocation(final String
includeLocationConfigValue) {
if (includeLocationConfigValue == null) {
final boolean sync = !AsyncLoggerContextSelector.isSelected();
return sync;
}
return Boolean.parseBoolean(includeLocationConfigValue);
}
{code}
> Serialize configuration into a log4j2.xml file
> --
>
> Key: LOG4J2-1528
> URL: https://issues.apache.org/jira/browse/LOG4J2-1528
> Project: Log4j 2
> Issue Type: New Feature
> Components: Configurators
>Affects Versions: 2.6.2
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
>
> This would be useful for e.g. converting from Log4j 1 to Log4j 2 config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429739#comment-15429739 ] Remko Popma commented on LOG4J2-1528: - Away from PC now but from memory the default is to *not* include location because of its severe performance impact. If ConfigurationBuilder includes location by default then that is a bug. Nice catch! > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429727#comment-15429727 ] Mikael Ståldal commented on LOG4J2-1528: I tried to put this in AbstractConfiguration, and that almost works too. The only problem is that I cannot get the StatusLogger configuration. Now both of them are in the branch. > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[
https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429642#comment-15429642
]
Mikael Ståldal commented on LOG4J2-1528:
{{ConfigurationBuilder.newLogger(String, Level)}} and
{{ConfigurationBuilder.newRootLogger(Level)}} set includeLocation to true by
default.
Is that how it should be? Is that consistent with configuration files?
Judging from {{LoggerConfig.includeLocation}} it seems like includeLocation on
loggers is a tri-state option where the absence is different from either true
or false.
But this absence of includeLocation is not possible to express with
ConfigurationBuilder currently. Should it be?
> Serialize configuration into a log4j2.xml file
> --
>
> Key: LOG4J2-1528
> URL: https://issues.apache.org/jira/browse/LOG4J2-1528
> Project: Log4j 2
> Issue Type: New Feature
> Components: Configurators
>Affects Versions: 2.6.2
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
>
> This would be useful for e.g. converting from Log4j 1 to Log4j 2 config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429640#comment-15429640 ] Mikael Ståldal commented on LOG4J2-1528: Added unit test. > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429468#comment-15429468 ] Mikael Ståldal commented on LOG4J2-1528: Reminding [~ralphgoers]... > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428764#comment-15428764 ] Mikael Ståldal commented on LOG4J2-1528: OK, changed. > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[
https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426515#comment-15426515
]
Remko Popma commented on LOG4J2-1528:
-
A method returning the current object as a string in some format is
traditionally named {{toFormat}} or {{asFormat}}. I don't think there's a
convention for methods returning void that write the current object into a
parameter but {{writeAsFormat}} would be a good candidate. The current name is
ok too, although you may not need "File" at the end. It should _not_ be called
toSomething I think.
> Serialize configuration into a log4j2.xml file
> --
>
> Key: LOG4J2-1528
> URL: https://issues.apache.org/jira/browse/LOG4J2-1528
> Project: Log4j 2
> Issue Type: New Feature
> Components: Configurators
>Affects Versions: 2.6.2
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
>
> This would be useful for e.g. converting from Log4j 1 to Log4j 2 config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[
https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426308#comment-15426308
]
Mikael Ståldal commented on LOG4J2-1528:
What about the other method {{void writeXmlConfigurationFile(OutputStream
output)}}? Should it be "toXmlConfigurationFile"?
> Serialize configuration into a log4j2.xml file
> --
>
> Key: LOG4J2-1528
> URL: https://issues.apache.org/jira/browse/LOG4J2-1528
> Project: Log4j 2
> Issue Type: New Feature
> Components: Configurators
>Affects Versions: 2.6.2
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
>
> This would be useful for e.g. converting from Log4j 1 to Log4j 2 config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[
https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426305#comment-15426305
]
Mikael Ståldal commented on LOG4J2-1528:
Comment from [~garydgregory]:
{{String writeXmlConfiguration();}}
IMO this should be called "toXmlConfiguration", you like "toThis",
"toThat", for example "toString()".
> Serialize configuration into a log4j2.xml file
> --
>
> Key: LOG4J2-1528
> URL: https://issues.apache.org/jira/browse/LOG4J2-1528
> Project: Log4j 2
> Issue Type: New Feature
> Components: Configurators
>Affects Versions: 2.6.2
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
>
> This would be useful for e.g. converting from Log4j 1 to Log4j 2 config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426303#comment-15426303 ] Mikael Ståldal commented on LOG4J2-1528: My impression is that XML is the "main" configuration format for Log4j 2. That's the impression you get from our documentation. I also prefer and always use XML config myself. I was able to do this XML serialization without any extra dependencies (using only standard Java APIs). I think it would be quite easy to do the same for JSON/YAML also, but that might bring in extra dependencies like Jackson (there are no standard Java APIs for JSON or YAML as far as I know). > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426298#comment-15426298 ] Mikael Ståldal commented on LOG4J2-1528: OK, link removed. I still think this could be useful for converting from Log4j 1 config, but let's take that discussion elsewhere. Anyway this feature is useful in its own right. > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425621#comment-15425621 ] Ralph Goers commented on LOG4J2-1528: - True. I personally prefer XML over JSON for the Log4j configuration. > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425342#comment-15425342 ] Gary Gregory commented on LOG4J2-1528: -- You know someone will ask "But what about JSON?" ;-) > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425301#comment-15425301 ] Ralph Goers commented on LOG4J2-1528: - I'll take a look but probably won't get a chance until the weekend. Please remind me. > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[
https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425295#comment-15425295
]
Mikael Ståldal commented on LOG4J2-1528:
It seems tricky to do this on an arbitrary
{{org.apache.logging.log4j.core.config.Configuration}} object.
However, doing it from
{{org.apache.logging.log4j.core.config.builder.api.ConfigurationBuilder}} is
quite easy.
See Git branch LOG4J2-1528. What do you think?
> Serialize configuration into a log4j2.xml file
> --
>
> Key: LOG4J2-1528
> URL: https://issues.apache.org/jira/browse/LOG4J2-1528
> Project: Log4j 2
> Issue Type: New Feature
> Components: Configurators
>Affects Versions: 2.6.2
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
>
> This would be useful for e.g. converting from Log4j 1 to Log4j 2 config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file
[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425283#comment-15425283 ] Ralph Goers commented on LOG4J2-1528: - LOG4J2-1525 should not be dependent on this as that is not the only way it can be implemented (nor is it likely to be). > Serialize configuration into a log4j2.xml file > -- > > Key: LOG4J2-1528 > URL: https://issues.apache.org/jira/browse/LOG4J2-1528 > Project: Log4j 2 > Issue Type: New Feature > Components: Configurators >Affects Versions: 2.6.2 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > This would be useful for e.g. converting from Log4j 1 to Log4j 2 config. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
