[
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
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
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
[
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
[
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
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:
[
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
[
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
[
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
[
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
[
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.
*
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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:
-
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
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:
[
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.
[
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
[
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
[
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
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
[
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
[
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
[
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
[
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?" ;-)
>
[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
[
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://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
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
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
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
[
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
>
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
[
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
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 =
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,
[
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
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
52 matches
Mail list logo