Re: logging-log4j2 git commit: LOG4J2-1526 Possibility to set StatusLogger destination in ConfigurationBuilder

[Gary Gregory]

Or:

status = ERROR
status.destination = err

Gary

On Wed, Aug 17, 2016 at 8:10 PM, Remko Popma  wrote:

> Can we change the naming to make configuration more intuitive? At first
> glance there's no way to see that these two lines are related:
>
>  status = ERROR
> +dest = err
>
> How about something like this?
>
> status = ERROR
> statusDestination = err
>
> Sent from my iPhone
>
> > On 2016/08/18, at 4:54, mi...@apache.org wrote:
> >
> > status = ERROR
> > +dest = err
>
> -
> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
>
>


-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition

JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: logging-log4j2 git commit: LOG4J2-1526 Possibility to set StatusLogger destination in ConfigurationBuilder

[Remko Popma]

Can we change the naming to make configuration more intuitive? At first glance 
there's no way to see that these two lines are related:

 status = ERROR
+dest = err

How about something like this?

status = ERROR
statusDestination = err

Sent from my iPhone

> On 2016/08/18, at 4:54, mi...@apache.org wrote:
> 
> status = ERROR
> +dest = err

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Updated] (LOG4J2-1529) composite configurations do not merge attributes on logger nodes

[Sridevi Narra (JIRA)]

 [ 
https://issues.apache.org/jira/browse/LOG4J2-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sridevi Narra updated LOG4J2-1529:
--
Description: 
According to Log4j2 Composite configuration documentation 
(https://logging.apache.org/log4j/2.x/manual/configuration.html#CompositeConfiguration)
 as given below, logger attributes should be merged.
"Loggers are all aggregated. Logger attributes are individually merged with 
duplicates being replaced by those in later configurations. ..."

However, if I have a 2 files that are composed with different Root Logger 
levels as given below, only the root level is used. I am not able to override 
the root logger level in the second file.

file1.xml:
{code}

  

  

  
  





{code}

file2.xml:
{code}

  





{code}

Command line arg:
-Dlog4j.configurationFile=file1.xml,file2.xml

Actual: The resulting log level is "warn"
Expected: log level to be "info"

  was:
According to Log4j2 Composite configuration documentation 
(https://logging.apache.org/log4j/2.x/manual/configuration.html#CompositeConfiguration)
 as given below, logger attributes should be merged.
"Loggers are all aggregated. Logger attributes are individually merged with 
duplicates being replaced by those in later configurations. ..."

However, if I have a 2 files that are composed with different Root Logger 
levels as given below, only the root level is used. I am not able to override 
the root logger level in the second file.

file1.xml:

  

  

  
  






file2.xml:

  






Command line arg:
-Dlog4j.configurationFile=file1.xml,file2.xml

Actual: The resulting log level is "warn"
Expected: log level to be "info"


> composite configurations do not merge attributes on logger nodes
> 
>
> Key: LOG4J2-1529
> URL: https://issues.apache.org/jira/browse/LOG4J2-1529
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 2.6.2
>Reporter: Sridevi Narra
>
> According to Log4j2 Composite configuration documentation 
> (https://logging.apache.org/log4j/2.x/manual/configuration.html#CompositeConfiguration)
>  as given below, logger attributes should be merged.
> "Loggers are all aggregated. Logger attributes are individually merged with 
> duplicates being replaced by those in later configurations. ..."
> However, if I have a 2 files that are composed with different Root Logger 
> levels as given below, only the root level is used. I am not able to override 
> the root logger level in the second file.
> file1.xml:
> {code}
> 
>   
> 
>   
> 
>   
>   
> 
> 
> 
> 
> 
> {code}
> file2.xml:
> {code}
> 
>   
> 
> 
> 
> 
> 
> {code}
> Command line arg:
> -Dlog4j.configurationFile=file1.xml,file2.xml
> Actual: The resulting log level is "warn"
> Expected: log level to be "info"



--
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] [Created] (LOG4J2-1529) composite configurations do not merge attributes on logger nodes

[Sridevi Narra (JIRA)]

Sridevi Narra created LOG4J2-1529:
-

 Summary: composite configurations do not merge attributes on 
logger nodes
 Key: LOG4J2-1529
 URL: https://issues.apache.org/jira/browse/LOG4J2-1529
 Project: Log4j 2
  Issue Type: Bug
  Components: Core
Affects Versions: 2.6.2
Reporter: Sridevi Narra


According to Log4j2 Composite configuration documentation 
(https://logging.apache.org/log4j/2.x/manual/configuration.html#CompositeConfiguration)
 as given below, logger attributes should be merged.
"Loggers are all aggregated. Logger attributes are individually merged with 
duplicates being replaced by those in later configurations. ..."

However, if I have a 2 files that are composed with different Root Logger 
levels as given below, only the root level is used. I am not able to override 
the root logger level in the second file.

file1.xml:

  

  

  
  






file2.xml:

  






Command line arg:
-Dlog4j.configurationFile=file1.xml,file2.xml

Actual: The resulting log level is "warn"
Expected: log level to be "info"



--
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

[Ralph Goers (JIRA)]

[ 
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

Fwd: failure notice

[Gary Gregory]

[Re-sending, got a mailer error]

>
> +/**
> + * Write an XML configuration from this builder.
> + *
> + * @return  XML configuration
> + */
> +String writeXmlConfiguration();
>

IMO this should be called "toXmlConfiguration", you like "toThis",
"toThat", for example "toString()".

Gary

[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file

[Gary Gregory (JIRA)]

[ 
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

[Ralph Goers (JIRA)]

[ 
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

[JIRA]

[ 
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

[Ralph Goers (JIRA)]

[ 
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

[jira] [Commented] (LOG4J2-1524) Support overall structure of Log4j 1 log4j.properties

[Ralph Goers (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425279#comment-15425279
 ] 

Ralph Goers commented on LOG4J2-1524:
-

I didn't mean to imply that a Log4j 1 configuration would create Log4j 2 
Configuration objects. More likely, a Log4j 1 configuration file will be 
translated into a Log4j 2 configuration file.

> Support overall structure of Log4j 1 log4j.properties
> -
>
> Key: LOG4J2-1524
> URL: https://issues.apache.org/jira/browse/LOG4J2-1524
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Configurators
>Reporter: Mikael Ståldal
> Fix For: 2.7
>
>
> We need some tests for this.



--
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-1524) Support overall structure of Log4j 1 log4j.properties

[JIRA]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425260#comment-15425260
 ] 

Mikael Ståldal commented on LOG4J2-1524:


See LOG4J2-1528

> Support overall structure of Log4j 1 log4j.properties
> -
>
> Key: LOG4J2-1524
> URL: https://issues.apache.org/jira/browse/LOG4J2-1524
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Configurators
>Reporter: Mikael Ståldal
> Fix For: 2.7
>
>
> We need some tests for this.



--
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

Re: Configuration

[Mikael Ståldal]

I have created a JIRA issue for this:
https://issues.apache.org/jira/browse/LOG4J2-1528

On Aug 14, 2016 11:02 PM, "Gary Gregory"  wrote:

> I guess not. If we based our config parser on Jackson, that would be an
> easy yes, but would require a dependency that most people would find odd.
> We could also base configuration on JAXB then you would get XML IO. For
> JSON, there is a new JAXB like JSR IIRC.
>
> Gary
>
> On Aug 14, 2016 1:14 PM, "Mikael Ståldal" 
> wrote:
>
>> Is there a way to serialize a Configuration into one of the config file
>> formats we support?
>>
>

[jira] [Created] (LOG4J2-1528) Serialize configuration into a log4j2.xml file

[JIRA]

Mikael Ståldal created LOG4J2-1528:
--

 Summary: 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] [Resolved] (LOG4J2-1526) Possibility to set StatusLogger destination in ConfigurationBuilder

[JIRA]

 [ 
https://issues.apache.org/jira/browse/LOG4J2-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikael Ståldal resolved LOG4J2-1526.

   Resolution: Fixed
Fix Version/s: 2.7

Fixed in master branch. I added this to {{PropertiesConfigurationBuilder}} also.

> Possibility to set StatusLogger destination in ConfigurationBuilder
> ---
>
> Key: LOG4J2-1526
> URL: https://issues.apache.org/jira/browse/LOG4J2-1526
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: Configurators
>Affects Versions: 2.6.2
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
> Fix For: 2.7
>
>
> We are missing a method to set StatusLogger destination (corresponding to the 
> "dest" root attribute in config files, and 
> {{org.apache.logging.log4j.core.config.status.StatusConfiguration#withDestination}})
>  in {{org.apache.logging.log4j.core.config.builder.api.ConfigurationBuilder}}.



--
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] [Assigned] (LOG4J2-1526) Possibility to set StatusLogger destination in ConfigurationBuilder

[JIRA]

 [ 
https://issues.apache.org/jira/browse/LOG4J2-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikael Ståldal reassigned LOG4J2-1526:
--

Assignee: Mikael Ståldal

> Possibility to set StatusLogger destination in ConfigurationBuilder
> ---
>
> Key: LOG4J2-1526
> URL: https://issues.apache.org/jira/browse/LOG4J2-1526
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: Configurators
>Affects Versions: 2.6.2
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
>
> We are missing a method to set StatusLogger destination (corresponding to the 
> "dest" root attribute in config files, and 
> {{org.apache.logging.log4j.core.config.status.StatusConfiguration#withDestination}})
>  in {{org.apache.logging.log4j.core.config.builder.api.ConfigurationBuilder}}.



--
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-1527) NPE thrown when log4j2 used within a webapp and RingBufferLogEvent's getFormattedMessage() is called.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425176#comment-15425176
 ] 

ASF GitHub Bot commented on LOG4J2-1527:


GitHub user leonj1 opened a pull request:

https://github.com/apache/logging-log4j2/pull/39

LOG4J2-1527 - Add a null check in getFormattedMessage and initialize when 
needed

One way to see this problem is by changing 
"GcFreeLoggingTestUtil.executeLogging()"
from: System.setProperty("log4j2.is.webapp", "false");
to: System.setProperty("log4j2.is.webapp", "true");


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/leonj1/logging-log4j2 
bugfix_prevent_npe_on_getFormattedMessage

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/logging-log4j2/pull/39.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #39


commit c5430dbb2c14cf8753439cf331991187ce4d164d
Author: Jose Leon 
Date:   2016-08-17T18:54:43Z

LOG4J2-1527 - Add a null check in getFormattedMessage and initialize when 
needed




> NPE thrown when log4j2 used within a webapp and RingBufferLogEvent's 
> getFormattedMessage() is called.
> -
>
> Key: LOG4J2-1527
> URL: https://issues.apache.org/jira/browse/LOG4J2-1527
> Project: Log4j 2
>  Issue Type: Bug
>Affects Versions: 2.6.2
>Reporter: Jose Leon
>
> This happens because 'messageText' is never initialized, therefore "return 
> messageText.toString();" throws the NPE.



--
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] [Created] (LOG4J2-1527) NPE thrown when log4j2 used within a webapp and RingBufferLogEvent's getFormattedMessage() is called.

[Jose Leon (JIRA)]

Jose Leon created LOG4J2-1527:
-

 Summary: NPE thrown when log4j2 used within a webapp and 
RingBufferLogEvent's getFormattedMessage() is called.
 Key: LOG4J2-1527
 URL: https://issues.apache.org/jira/browse/LOG4J2-1527
 Project: Log4j 2
  Issue Type: Bug
Affects Versions: 2.6.2
Reporter: Jose Leon


This happens because 'messageText' is never initialized, therefore "return 
messageText.toString();" throws the NPE.



--
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] [Comment Edited] (LOG4J2-1522) Log4j 1 layouts

[Gary Gregory (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425109#comment-15425109
 ] 

Gary Gregory edited comment on LOG4J2-1522 at 8/17/16 6:31 PM:
---

Maybe {{variablesNotEmpty\{pattern\}}} can be used here? Or a variation?



was (Author: garydgregory):
Maybe {{variablesNotEmpty{pattern}}} can be used here? Or a variation?


> Log4j 1 layouts
> ---
>
> Key: LOG4J2-1522
> URL: https://issues.apache.org/jira/browse/LOG4J2-1522
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Layouts
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
> Fix For: 2.7
>
>
> Support all layouts in Log4j 1 to the extent possible an reasonable.
> * PatternLayout and EnhancedPatternLayout are mapped to PatternLayout. We 
> provide two new pattern conversions for the Log4j 1 format of NDC and MDC.
> * SimpleLayout is mapped to PatternLayout "%level - %m%n"
> * TTCCLayout is ported (cannot be emulated exactly with PatternLayout)
> * HTMLLayout is mapped to HtmlLayout (will not look exactly the same, but 
> close enough)
> * XMLLayout is ported (XmlLayout in Log4j 2 is different and will not work)



--
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-1522) Log4j 1 layouts

[Gary Gregory (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425109#comment-15425109
 ] 

Gary Gregory commented on LOG4J2-1522:
--

Maybe {{variablesNotEmpty{pattern}}} can be used here? Or a variation?


> Log4j 1 layouts
> ---
>
> Key: LOG4J2-1522
> URL: https://issues.apache.org/jira/browse/LOG4J2-1522
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Layouts
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
> Fix For: 2.7
>
>
> Support all layouts in Log4j 1 to the extent possible an reasonable.
> * PatternLayout and EnhancedPatternLayout are mapped to PatternLayout. We 
> provide two new pattern conversions for the Log4j 1 format of NDC and MDC.
> * SimpleLayout is mapped to PatternLayout "%level - %m%n"
> * TTCCLayout is ported (cannot be emulated exactly with PatternLayout)
> * HTMLLayout is mapped to HtmlLayout (will not look exactly the same, but 
> close enough)
> * XMLLayout is ported (XmlLayout in Log4j 2 is different and will not work)



--
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-1522) Log4j 1 layouts

[Ralph Goers (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425054#comment-15425054
 ] 

Ralph Goers commented on LOG4J2-1522:
-

TTCC_CONVERSION_PATTERN is a static constant in the PatternLayout. It appears I 
didn't add a way to specify it or the SIMPLE_CONVERSION_PATTERN. I believe all 
that is required is for those to be able to be specified as the pattern to use.

> Log4j 1 layouts
> ---
>
> Key: LOG4J2-1522
> URL: https://issues.apache.org/jira/browse/LOG4J2-1522
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Layouts
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
> Fix For: 2.7
>
>
> Support all layouts in Log4j 1 to the extent possible an reasonable.
> * PatternLayout and EnhancedPatternLayout are mapped to PatternLayout. We 
> provide two new pattern conversions for the Log4j 1 format of NDC and MDC.
> * SimpleLayout is mapped to PatternLayout "%level - %m%n"
> * TTCCLayout is ported (cannot be emulated exactly with PatternLayout)
> * HTMLLayout is mapped to HtmlLayout (will not look exactly the same, but 
> close enough)
> * XMLLayout is ported (XmlLayout in Log4j 2 is different and will not work)



--
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-1526) Possibility to set StatusLogger destination in ConfigurationBuilder

[Ralph Goers (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425033#comment-15425033
 ] 

Ralph Goers commented on LOG4J2-1526:
-

It is an oversight. It should be added.

> Possibility to set StatusLogger destination in ConfigurationBuilder
> ---
>
> Key: LOG4J2-1526
> URL: https://issues.apache.org/jira/browse/LOG4J2-1526
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: Configurators
>Affects Versions: 2.6.2
>Reporter: Mikael Ståldal
>
> We are missing a method to set StatusLogger destination (corresponding to the 
> "dest" root attribute in config files, and 
> {{org.apache.logging.log4j.core.config.status.StatusConfiguration#withDestination}})
>  in {{org.apache.logging.log4j.core.config.builder.api.ConfigurationBuilder}}.



--
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-1526) Possibility to set StatusLogger destination in ConfigurationBuilder

[JIRA]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425023#comment-15425023
 ] 

Mikael Ståldal commented on LOG4J2-1526:


[~ralphgoers] Was this left out intentionally, or was it just an oversight?

> Possibility to set StatusLogger destination in ConfigurationBuilder
> ---
>
> Key: LOG4J2-1526
> URL: https://issues.apache.org/jira/browse/LOG4J2-1526
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: Configurators
>Affects Versions: 2.6.2
>Reporter: Mikael Ståldal
>
> We are missing a method to set StatusLogger destination (corresponding to the 
> "dest" root attribute in config files, and 
> {{org.apache.logging.log4j.core.config.status.StatusConfiguration#withDestination}})
>  in {{org.apache.logging.log4j.core.config.builder.api.ConfigurationBuilder}}.



--
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-1522) Log4j 1 layouts

[JIRA]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425021#comment-15425021
 ] 

Mikael Ståldal commented on LOG4J2-1522:


Yes, maybe. What's missing is the possibility to add a space before/after a 
value if it exists. Like:

{{foo bar baz}} when "bar" have a value but {{foo baz}} when "bar" is empty. 
(Used for the context stack.)

Could be a useful generic feature to add to PatternLayout, and if we do then we 
would not need TTCCLayout.


> Log4j 1 layouts
> ---
>
> Key: LOG4J2-1522
> URL: https://issues.apache.org/jira/browse/LOG4J2-1522
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Layouts
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
> Fix For: 2.7
>
>
> Support all layouts in Log4j 1 to the extent possible an reasonable.
> * PatternLayout and EnhancedPatternLayout are mapped to PatternLayout. We 
> provide two new pattern conversions for the Log4j 1 format of NDC and MDC.
> * SimpleLayout is mapped to PatternLayout "%level - %m%n"
> * TTCCLayout is ported (cannot be emulated exactly with PatternLayout)
> * HTMLLayout is mapped to HtmlLayout (will not look exactly the same, but 
> close enough)
> * XMLLayout is ported (XmlLayout in Log4j 2 is different and will not work)



--
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-1522) Log4j 1 layouts

[Gary Gregory (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424922#comment-15424922
 ] 

Gary Gregory commented on LOG4J2-1522:
--

Can't the {{PatternLayout}} be reasonably enhanced to support {{TTCCLayout}}?

> Log4j 1 layouts
> ---
>
> Key: LOG4J2-1522
> URL: https://issues.apache.org/jira/browse/LOG4J2-1522
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Layouts
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
> Fix For: 2.7
>
>
> Support all layouts in Log4j 1 to the extent possible an reasonable.
> * PatternLayout and EnhancedPatternLayout are mapped to PatternLayout. We 
> provide two new pattern conversions for the Log4j 1 format of NDC and MDC.
> * SimpleLayout is mapped to PatternLayout "%level - %m%n"
> * TTCCLayout is ported (cannot be emulated exactly with PatternLayout)
> * HTMLLayout is mapped to HtmlLayout (will not look exactly the same, but 
> close enough)
> * XMLLayout is ported (XmlLayout in Log4j 2 is different and will not work)



--
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] [Created] (LOG4J2-1526) Possibility to set StatusLogger destination in ConfigurationBuilder

[JIRA]

Mikael Ståldal created LOG4J2-1526:
--

 Summary: Possibility to set StatusLogger destination in 
ConfigurationBuilder
 Key: LOG4J2-1526
 URL: https://issues.apache.org/jira/browse/LOG4J2-1526
 Project: Log4j 2
  Issue Type: Improvement
  Components: Configurators
Affects Versions: 2.6.2
Reporter: Mikael Ståldal


We are missing a method to set StatusLogger destination (corresponding to the 
"dest" root attribute in config files, and 
{{org.apache.logging.log4j.core.config.status.StatusConfiguration#withDestination}})
 in {{org.apache.logging.log4j.core.config.builder.api.ConfigurationBuilder}}.



--
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-1525) Convert Log4j 1 log4j.properties into equvivalent Log4j 2 config file

[JIRA]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424889#comment-15424889
 ] 

Mikael Ståldal commented on LOG4J2-1525:


The XmlLayout in Log4j 2 produce a different output format than XMLLayout in 
Log4j 1. Both produce XML, but with different schemas.

I did not find anything like TTCCLayout in Log4j 2.


> Convert Log4j 1 log4j.properties into equvivalent Log4j 2 config file
> -
>
> Key: LOG4J2-1525
> URL: https://issues.apache.org/jira/browse/LOG4J2-1525
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Configurators
>Reporter: Mikael Ståldal
> Fix For: 2.7
>
>




--
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-1525) Convert Log4j 1 log4j.properties into equvivalent Log4j 2 config file

[Ralph Goers (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424878#comment-15424878
 ] 

Ralph Goers commented on LOG4J2-1525:
-

I am confused. XMLLayout started from the Log4j 1 XMLLayout.  I don't recall 
what TTCCLayout is but I thought I had ported them all to Log4j 2.

What are we going to gain from this?

> Convert Log4j 1 log4j.properties into equvivalent Log4j 2 config file
> -
>
> Key: LOG4J2-1525
> URL: https://issues.apache.org/jira/browse/LOG4J2-1525
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Configurators
>Reporter: Mikael Ståldal
> Fix For: 2.7
>
>




--
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-1524) Support overall structure of Log4j 1 log4j.properties

[Ralph Goers (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424859#comment-15424859
 ] 

Ralph Goers commented on LOG4J2-1524:
-

While that may be true from a technical point of view, we really don't want to 
encourage the use of Log4j 1 configurations. For one, they are going to require 
more overhead as they will essentially first have to be converted to a Log4j 2 
configuration format and then have that configuration be used. With that , the 
configuration might as well be saved for reuse.

> Support overall structure of Log4j 1 log4j.properties
> -
>
> Key: LOG4J2-1524
> URL: https://issues.apache.org/jira/browse/LOG4J2-1524
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Configurators
>Reporter: Mikael Ståldal
> Fix For: 2.7
>
>
> We need some tests for this.



--
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] [Updated] (LOG4J2-1523) Log4j 1 appenders

[JIRA]

 [ 
https://issues.apache.org/jira/browse/LOG4J2-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikael Ståldal updated LOG4J2-1523:
---
Description: 
Support all appenders in Log4j 1 to the extent possible and reasonable.

All appenders in Log4j 1:
* AsyncAppender
* RewriteAppender
* NullAppender
* ConsoleAppender
* FileAppender
* RollingFileAppender
* DailyRollingFileAppender
* ExternallyRolledFileAppender
* JDBCAppender
* JMSAppender
* SMTPAppender
* SocketAppender
* SocketHubAppender
* SyslogAppender
* TelnetAppender
* NTEventLogAppender
* WriterAppender
* VectorAppender
* LF5Appender (?)


  was:
Support all appenders in Log4j 1 to the extent possible and reasonable.

All appenders in Log4j 1:
* AsyncAppender
* RewriteAppender
* NullAppender
* ConsoleAppender
* FileAppender
* RollingFileAppender
* DailyRollingFileAppender
* ExternallyRolledFileAppender
* JDBCAppender
* JMSAppender
* SMTPAppender
* SocketAppender
* SocketHubAppender
* SyslogAppender
* TelnetAppender
* NTEventLogAppender
* WriterAppender
* VectorAppender



> Log4j 1 appenders
> -
>
> Key: LOG4J2-1523
> URL: https://issues.apache.org/jira/browse/LOG4J2-1523
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Appenders
>Reporter: Mikael Ståldal
> Fix For: 2.7
>
>
> Support all appenders in Log4j 1 to the extent possible and reasonable.
> All appenders in Log4j 1:
> * AsyncAppender
> * RewriteAppender
> * NullAppender
> * ConsoleAppender
> * FileAppender
> * RollingFileAppender
> * DailyRollingFileAppender
> * ExternallyRolledFileAppender
> * JDBCAppender
> * JMSAppender
> * SMTPAppender
> * SocketAppender
> * SocketHubAppender
> * SyslogAppender
> * TelnetAppender
> * NTEventLogAppender
> * WriterAppender
> * VectorAppender
> * LF5Appender (?)



--
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] [Comment Edited] (LOG4J2-1523) Log4j 1 appenders

[JIRA]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424720#comment-15424720
 ] 

Mikael Ståldal edited comment on LOG4J2-1523 at 8/17/16 3:31 PM:
-

According to Log4j 1 Javadoc, there is 
[LF5Appender|http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/lf5/LF5Appender.html],
 but I cannot find the source code for that.


was (Author: mikaelstaldal):
According to Log4j 1 Javadoc, there is also 
[LF5Appender|http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/lf5/LF5Appender.html],
 but I cannot find the source code for that.

> Log4j 1 appenders
> -
>
> Key: LOG4J2-1523
> URL: https://issues.apache.org/jira/browse/LOG4J2-1523
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Appenders
>Reporter: Mikael Ståldal
> Fix For: 2.7
>
>
> Support all appenders in Log4j 1 to the extent possible and reasonable.
> All appenders in Log4j 1:
> * AsyncAppender
> * RewriteAppender
> * NullAppender
> * ConsoleAppender
> * FileAppender
> * RollingFileAppender
> * DailyRollingFileAppender
> * ExternallyRolledFileAppender
> * JDBCAppender
> * JMSAppender
> * SMTPAppender
> * SocketAppender
> * SocketHubAppender
> * SyslogAppender
> * TelnetAppender
> * NTEventLogAppender
> * WriterAppender
> * VectorAppender
> * LF5Appender (?)



--
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-1523) Log4j 1 appenders

[JIRA]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424720#comment-15424720
 ] 

Mikael Ståldal commented on LOG4J2-1523:


According to Log4j 1 Javadoc, there is also 
[LF5Appender|http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/lf5/LF5Appender.html],
 but I cannot find the source code for that.

> Log4j 1 appenders
> -
>
> Key: LOG4J2-1523
> URL: https://issues.apache.org/jira/browse/LOG4J2-1523
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Appenders
>Reporter: Mikael Ståldal
> Fix For: 2.7
>
>
> Support all appenders in Log4j 1 to the extent possible and reasonable.
> All appenders in Log4j 1:
> * AsyncAppender
> * RewriteAppender
> * NullAppender
> * ConsoleAppender
> * FileAppender
> * RollingFileAppender
> * DailyRollingFileAppender
> * ExternallyRolledFileAppender
> * JDBCAppender
> * JMSAppender
> * SMTPAppender
> * SocketAppender
> * SocketHubAppender
> * SyslogAppender
> * TelnetAppender
> * NTEventLogAppender
> * WriterAppender
> * VectorAppender



--
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] [Updated] (LOG4J2-1523) Log4j 1 appenders

[JIRA]

 [ 
https://issues.apache.org/jira/browse/LOG4J2-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikael Ståldal updated LOG4J2-1523:
---
Description: 
Support all appenders in Log4j 1 to the extent possible and reasonable.

All appenders in Log4j 1:
* AsyncAppender
* RewriteAppender
* NullAppender
* ConsoleAppender
* FileAppender
* RollingFileAppender
* DailyRollingFileAppender
* ExternallyRolledFileAppender
* JDBCAppender
* JMSAppender
* SMTPAppender
* SocketAppender
* SocketHubAppender
* SyslogAppender
* TelnetAppender
* NTEventLogAppender
* WriterAppender
* VectorAppender


  was:Support all appenders in Log4j 1 to the extent possible and reasonable.


> Log4j 1 appenders
> -
>
> Key: LOG4J2-1523
> URL: https://issues.apache.org/jira/browse/LOG4J2-1523
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Appenders
>Reporter: Mikael Ståldal
> Fix For: 2.7
>
>
> Support all appenders in Log4j 1 to the extent possible and reasonable.
> All appenders in Log4j 1:
> * AsyncAppender
> * RewriteAppender
> * NullAppender
> * ConsoleAppender
> * FileAppender
> * RollingFileAppender
> * DailyRollingFileAppender
> * ExternallyRolledFileAppender
> * JDBCAppender
> * JMSAppender
> * SMTPAppender
> * SocketAppender
> * SocketHubAppender
> * SyslogAppender
> * TelnetAppender
> * NTEventLogAppender
> * WriterAppender
> * VectorAppender



--
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-1525) Convert Log4j 1 log4j.properties into equvivalent Log4j 2 config file

[JIRA]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424681#comment-15424681
 ] 

Mikael Ståldal commented on LOG4J2-1525:


I think it's better to port the Log4j components we want, as I have done with 
TTCCLayout and XMLLayout. See classes in {{org.apache.log4j.layout}}.

> Convert Log4j 1 log4j.properties into equvivalent Log4j 2 config file
> -
>
> Key: LOG4J2-1525
> URL: https://issues.apache.org/jira/browse/LOG4J2-1525
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Configurators
>Reporter: Mikael Ståldal
> Fix For: 2.7
>
>




--
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-1522) Log4j 1 layouts

[JIRA]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424673#comment-15424673
 ] 

Mikael Ståldal commented on LOG4J2-1522:


Only reaming issue is that the format is slightly different for %x (NDC) and %X 
(MDC), see comment in {{Log4j1ConfigurationFactory.java}}. I added support for 
the Log4j formats if you use %ndc or %properties instead. Don't want to change 
the behaviour of existing conversions in Log4j's 2 PatternLayout.

I think this should be good enough if we document it.

> Log4j 1 layouts
> ---
>
> Key: LOG4J2-1522
> URL: https://issues.apache.org/jira/browse/LOG4J2-1522
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Layouts
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
> Fix For: 2.7
>
>
> Support all layouts in Log4j 1 to the extent possible an reasonable.
> * PatternLayout and EnhancedPatternLayout are mapped to PatternLayout. We 
> provide two new pattern conversions for the Log4j 1 format of NDC and MDC.
> * SimpleLayout is mapped to PatternLayout "%level - %m%n"
> * TTCCLayout is ported (cannot be emulated exactly with PatternLayout)
> * HTMLLayout is mapped to HtmlLayout (will not look exactly the same, but 
> close enough)
> * XMLLayout is ported (XmlLayout in Log4j 2 is different and will not work)



--
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] [Resolved] (LOG4J2-1522) Log4j 1 layouts

[JIRA]

 [ 
https://issues.apache.org/jira/browse/LOG4J2-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikael Ståldal resolved LOG4J2-1522.

Resolution: Fixed

See {{org.apache.log4j.config.Log4j1ConfigurationFactory#buildAppenderLayout}}.

> Log4j 1 layouts
> ---
>
> Key: LOG4J2-1522
> URL: https://issues.apache.org/jira/browse/LOG4J2-1522
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Layouts
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
> Fix For: 2.7
>
>
> Support all layouts in Log4j 1 to the extent possible an reasonable.
> * PatternLayout and EnhancedPatternLayout are mapped to PatternLayout. We 
> provide two new pattern conversions for the Log4j 1 format of NDC and MDC.
> * SimpleLayout is mapped to PatternLayout "%level - %m%n"
> * TTCCLayout is ported (cannot be emulated exactly with PatternLayout)
> * HTMLLayout is mapped to HtmlLayout (will not look exactly the same, but 
> close enough)
> * XMLLayout is ported (XmlLayout in Log4j 2 is different and will not work)



--
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-1522) Log4j 1 layouts

[JIRA]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424669#comment-15424669
 ] 

Mikael Ståldal commented on LOG4J2-1522:


We do not use the Log4j 1 layouts directly, we map them to a compatible layout 
in Log4j 2 if possible, or else port them to the Log4j 2 Layout interface.

> Log4j 1 layouts
> ---
>
> Key: LOG4J2-1522
> URL: https://issues.apache.org/jira/browse/LOG4J2-1522
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Layouts
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
> Fix For: 2.7
>
>
> Support all layouts in Log4j 1 to the extent possible an reasonable.
> * PatternLayout and EnhancedPatternLayout are mapped to PatternLayout. We 
> provide two new pattern conversions for the Log4j 1 format of NDC and MDC.
> * SimpleLayout is mapped to PatternLayout "%level - %m%n"
> * TTCCLayout is ported (cannot be emulated exactly with PatternLayout)
> * HTMLLayout is mapped to HtmlLayout (will not look exactly the same, but 
> close enough)
> * XMLLayout is ported (XmlLayout in Log4j 2 is different and will not work)



--
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-1522) Log4j 1 layouts

[JIRA]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424667#comment-15424667
 ] 

Mikael Ståldal commented on LOG4J2-1522:


The fact that Log4j 1 didn't support plugins makes this easier since we then 
have a fixed and limited set of layouts (six of them, see list in description) 
to handle.

> Log4j 1 layouts
> ---
>
> Key: LOG4J2-1522
> URL: https://issues.apache.org/jira/browse/LOG4J2-1522
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Layouts
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
> Fix For: 2.7
>
>
> Support all layouts in Log4j 1 to the extent possible an reasonable.
> * PatternLayout and EnhancedPatternLayout are mapped to PatternLayout. We 
> provide two new pattern conversions for the Log4j 1 format of NDC and MDC.
> * SimpleLayout is mapped to PatternLayout "%level - %m%n"
> * TTCCLayout is ported (cannot be emulated exactly with PatternLayout)
> * HTMLLayout is mapped to HtmlLayout (will not look exactly the same, but 
> close enough)
> * XMLLayout is ported (XmlLayout in Log4j 2 is different and will not work)



--
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] [Updated] (LOG4J2-1522) Log4j 1 layouts

[JIRA]

 [ 
https://issues.apache.org/jira/browse/LOG4J2-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikael Ståldal updated LOG4J2-1522:
---
Description: 
Support all layouts in Log4j 1 to the extent possible an reasonable.

* PatternLayout and EnhancedPatternLayout are mapped to PatternLayout. We 
provide two new pattern conversions for the Log4j 1 format of NDC and MDC.
* SimpleLayout is mapped to PatternLayout "%level - %m%n"
* TTCCLayout is ported (cannot be emulated exactly with PatternLayout)
* HTMLLayout is mapped to HtmlLayout (will not look exactly the same, but close 
enough)
* XMLLayout is ported (XmlLayout in Log4j 2 is different and will not work)

  was:Support all layouts in Log4j 1 to the extent possible an reasonable.


> Log4j 1 layouts
> ---
>
> Key: LOG4J2-1522
> URL: https://issues.apache.org/jira/browse/LOG4J2-1522
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Layouts
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
> Fix For: 2.7
>
>
> Support all layouts in Log4j 1 to the extent possible an reasonable.
> * PatternLayout and EnhancedPatternLayout are mapped to PatternLayout. We 
> provide two new pattern conversions for the Log4j 1 format of NDC and MDC.
> * SimpleLayout is mapped to PatternLayout "%level - %m%n"
> * TTCCLayout is ported (cannot be emulated exactly with PatternLayout)
> * HTMLLayout is mapped to HtmlLayout (will not look exactly the same, but 
> close enough)
> * XMLLayout is ported (XmlLayout in Log4j 2 is different and will not work)



--
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-1524) Support overall structure of Log4j 1 log4j.properties

[JIRA]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424627#comment-15424627
 ] 

Mikael Ståldal commented on LOG4J2-1524:


If we develop a way to serialize a Configuration object into a Log4j 2 config 
file, we can get both.

> Support overall structure of Log4j 1 log4j.properties
> -
>
> Key: LOG4J2-1524
> URL: https://issues.apache.org/jira/browse/LOG4J2-1524
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Configurators
>Reporter: Mikael Ståldal
> Fix For: 2.7
>
>
> We need some tests for this.



--
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-1522) Log4j 1 layouts

[JIRA]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424610#comment-15424610
 ] 

Mikael Ståldal commented on LOG4J2-1522:


It is already done, see my recent commits to master branch.

> Log4j 1 layouts
> ---
>
> Key: LOG4J2-1522
> URL: https://issues.apache.org/jira/browse/LOG4J2-1522
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Layouts
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
> Fix For: 2.7
>
>
> Support all layouts in Log4j 1 to the extent possible an reasonable.



--
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-1524) Support overall structure of Log4j 1 log4j.properties

[Ralph Goers (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424588#comment-15424588
 ] 

Ralph Goers commented on LOG4J2-1524:
-

I am not crazy about doing this at run time. I prefer the approach of using a 
tool to permanently convert the configuration file.

> Support overall structure of Log4j 1 log4j.properties
> -
>
> Key: LOG4J2-1524
> URL: https://issues.apache.org/jira/browse/LOG4J2-1524
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Configurators
>Reporter: Mikael Ståldal
> Fix For: 2.7
>
>
> We need some tests for this.



--
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-1525) Convert Log4j 1 log4j.properties into equvivalent Log4j 2 config file

[Ralph Goers (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424586#comment-15424586
 ] 

Ralph Goers commented on LOG4J2-1525:
-

If a meta-data file can be provided that maps Log4j 1 components to their Log4j 
2 counterparts this might be possible. In fact, using that same meta data it 
might be possible to build a Log4j 2 wrapper around Log4j 1 components.

> Convert Log4j 1 log4j.properties into equvivalent Log4j 2 config file
> -
>
> Key: LOG4J2-1525
> URL: https://issues.apache.org/jira/browse/LOG4J2-1525
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Configurators
>Reporter: Mikael Ståldal
> Fix For: 2.7
>
>




--
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-1523) Log4j 1 appenders

[Ralph Goers (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424577#comment-15424577
 ] 

Ralph Goers commented on LOG4J2-1523:
-

a) Why do we want to do this?
b) How can this be done?

Log4j 1 didn't support plugins and the interface was very different. I 
understand the motivation, but it would seem to me to be more reasonable to 
provide a tool to convert Log4j 1 configurations to the Log4j 2 configuration 
format, as much as possible.

I'd like to see more of a description of what is intended and how it can be 
accomplished.

> Log4j 1 appenders
> -
>
> Key: LOG4J2-1523
> URL: https://issues.apache.org/jira/browse/LOG4J2-1523
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Appenders
>Reporter: Mikael Ståldal
> Fix For: 2.7
>
>
> Support all appenders in Log4j 1 to the extent possible and reasonable.



--
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-1522) Log4j 1 layouts

[Ralph Goers (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424576#comment-15424576
 ] 

Ralph Goers commented on LOG4J2-1522:
-

a) Why do we want to do this?
b) How can this be done?

Log4j 1 didn't support plugins and the interface was very different. I 
understand the motivation, but it would seem to me to be more reasonable to 
provide a tool to convert Log4j 1 configurations to the Log4j 2 configuration 
format, as much as possible.

I'd like to see more of a description of what is intended and how it can be 
accomplished.

> Log4j 1 layouts
> ---
>
> Key: LOG4J2-1522
> URL: https://issues.apache.org/jira/browse/LOG4J2-1522
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Layouts
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
> Fix For: 2.7
>
>
> Support all layouts in Log4j 1 to the extent possible an reasonable.



--
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] [Updated] (LOG4J2-1524) Support overall structure of Log4j 1 log4j.properties

[JIRA]

 [ 
https://issues.apache.org/jira/browse/LOG4J2-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikael Ståldal updated LOG4J2-1524:
---
Description: We need some tests for this.

> Support overall structure of Log4j 1 log4j.properties
> -
>
> Key: LOG4J2-1524
> URL: https://issues.apache.org/jira/browse/LOG4J2-1524
> Project: Log4j 2
>  Issue Type: Sub-task
>  Components: Configurators
>Reporter: Mikael Ståldal
> Fix For: 2.7
>
>
> We need some tests for this.



--
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] [Created] (LOG4J2-1525) Convert Log4j 1 log4j.properties into equvivalent Log4j 2 config file

[JIRA]

Mikael Ståldal created LOG4J2-1525:
--

 Summary: Convert Log4j 1 log4j.properties into equvivalent Log4j 2 
config file
 Key: LOG4J2-1525
 URL: https://issues.apache.org/jira/browse/LOG4J2-1525
 Project: Log4j 2
  Issue Type: Sub-task
  Components: Configurators
Reporter: Mikael Ståldal






--
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] [Created] (LOG4J2-1524) Support overall structure of Log4j 1 log4j.properties

[JIRA]

Mikael Ståldal created LOG4J2-1524:
--

 Summary: Support overall structure of Log4j 1 log4j.properties
 Key: LOG4J2-1524
 URL: https://issues.apache.org/jira/browse/LOG4J2-1524
 Project: Log4j 2
  Issue Type: Sub-task
  Components: Configurators
Reporter: Mikael Ståldal






--
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] [Created] (LOG4J2-1523) Log4j 1 appenders

[JIRA]

Mikael Ståldal created LOG4J2-1523:
--

 Summary: Log4j 1 appenders
 Key: LOG4J2-1523
 URL: https://issues.apache.org/jira/browse/LOG4J2-1523
 Project: Log4j 2
  Issue Type: Sub-task
  Components: Appenders
Reporter: Mikael Ståldal


Support all appenders in Log4j 1 to the extent possible and reasonable.



--
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] [Created] (LOG4J2-1522) Log4j 1 layouts

[JIRA]

Mikael Ståldal created LOG4J2-1522:
--

 Summary: Log4j 1 layouts
 Key: LOG4J2-1522
 URL: https://issues.apache.org/jira/browse/LOG4J2-1522
 Project: Log4j 2
  Issue Type: Sub-task
  Components: Layouts
Reporter: Mikael Ståldal
Assignee: Mikael Ståldal


Support all layouts in Log4j 1 to the extent possible an reasonable.



--
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

Re: Migrating from Log4j 1

[Mikael Ståldal]

LOG4J2-63 reopened. I would need some help on it. Let't take discussions
about that in JIRA.

On Aug 15, 2016 10:48 AM, "Mikael Ståldal" 
wrote:

> Any objections to reopening LOG4J2-63, and targeting it for 2.7?
>
> On Sat, Aug 13, 2016 at 1:18 PM, Mikael Ståldal  > wrote:
>
>> Seems to be in https://issues.apache.org/jira/browse/LOG4J2-63
>>
>> It is currently marked as Won’t Fix. Should we reopen this issue?
>>
>> On Aug 13, 2016 1:04 PM, "Mikael Ståldal" 
>> wrote:
>>
>>> Do we have a JIRA issue to track this?
>>>
>>> On Aug 12, 2016 7:06 PM, "Gary Gregory"  wrote:
>>>
 Please consider expanding what I started here
 org.apache.log4j.config.Log4j1ConfigurationFactory

 Gary

 On Fri, Aug 12, 2016 at 9:52 AM, Mikael Ståldal <
 mikael.stal...@magine.com> wrote:

> There seem to be quite some frustration in some other Apache projects
> about migrating from Log4j 1. Especially around configration. Some seem to
> consider dropping Log4j completely instead of going for Log4j 2.
>
> I have taken on Spark, Hadoop and Zookeeper; see links to their Jira
> issues from LOG4J2-1473. I could need some help.
>



 --
 E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
 Java Persistence with Hibernate, Second Edition
 
 JUnit in Action, Second Edition 
 Spring Batch in Action 
 Blog: http://garygregory.wordpress.com
 Home: http://garygregory.com/
 Tweet! http://twitter.com/GaryGregory

>>>
>
>
> --
> [image: MagineTV]
>
> *Mikael Ståldal*
> Senior software developer
>
> *Magine TV*
> mikael.stal...@magine.com
> Grev Turegatan 3  | 114 46 Stockholm, Sweden  |   www.magine.com
>
> Privileged and/or Confidential Information may be contained in this
> message. If you are not the addressee indicated in this message
> (or responsible for delivery of the message to such a person), you may not
> copy or deliver this message to anyone. In such case,
> you should destroy this message and kindly notify the sender by reply
> email.
>

[jira] [Reopened] (LOG4J2-63) Support configuration from version 1.x log4j.properties

[JIRA]

 [ 
https://issues.apache.org/jira/browse/LOG4J2-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikael Ståldal reopened LOG4J2-63:
--
  Assignee: Mikael Ståldal

> Support configuration from version 1.x log4j.properties
> ---
>
> Key: LOG4J2-63
> URL: https://issues.apache.org/jira/browse/LOG4J2-63
> Project: Log4j 2
>  Issue Type: Wish
>  Components: Configurators
>Affects Versions: 2.6.2
>Reporter: Rogger Rabbit
>Assignee: Mikael Ståldal
> Fix For: 2.7
>
>
> Because i have not found the feature in project page: Please please support 
> configuration of Log4J 2 over the old fashioned properties file 
> (log4j.properties). It is the easiest understandable config format.



--
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