Hi,
Is there any way to change the string use for level ?
I'd like to use WARNING rather than WARN
Thanks
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe,
[
https://issues.apache.org/jira/browse/LOG4J2-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487184#comment-13487184
]
Ralph Goers commented on LOG4J2-95:
---
I have committed a fix and tested it in both Indigo
[
https://issues.apache.org/jira/browse/LOG4J2-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487195#comment-13487195
]
Ralph Goers commented on LOG4J2-96:
---
Can you describe your application a bit more so that
Hm, my goal is to use slf4j as api with log4j2.
I would prefer only provide a configuration file and to not have
specific log4j code introduced.
2012/10/30 Gary Gregory :
> Hm... in a custom layout I think...
>
> Gary
>
>
> On Tue, Oct 30, 2012 at 2:38 PM, Gary Gregory
> wrote:
>>
>> In 1.2, mayb
Where would you want the custom level name to appear?
Ralph
On Oct 30, 2012, at 2:05 PM, Olivier Lamy wrote:
> Hm, my goal is to use slf4j as api with log4j2.
> I would prefer only provide a configuration file and to not have
> specific log4j code introduced.
>
> 2012/10/30 Gary Gregory :
>> Hm
Do you want to use log4j 1.2.x or 2.0 (beta)?
Gary
On Tue, Oct 30, 2012 at 5:05 PM, Olivier Lamy wrote:
> Hm, my goal is to use slf4j as api with log4j2.
> I would prefer only provide a configuration file and to not have
> specific log4j code introduced.
>
> 2012/10/30 Gary Gregory :
> > Hm...
Ahh. Good question.
I was looking at LevelPatternConverter. It would be relatively trivial to allow
it to accept options so that you could specify %p{WARN=Warning,
ERROR=Error,FATAL=Critical}
Ralph
On Oct 30, 2012, at 2:10 PM, Gary Gregory wrote:
> Do you want to use log4j 1.2.x or 2.0 (b
2012/10/30 Ralph Goers :
> Ahh. Good question.
>
> I was looking at LevelPatternConverter. It would be relatively trivial to
> allow it to accept options so that you could specify %p{WARN=Warning,
> ERROR=Error,FATAL=Critical}
Great !
the goal is to use 2.0 (beta) (depending when that will be rele
FYII did a similar (reverse) thing so the default Android logging could
be slurped in to Chainsaw (with Android's single-letter severities)...so in
theory, you can still use Chainsaw to read log files with weird severity
names..
>From LogFilePatternReceiver sources:
/**
* If the log f
I'm not sure what you are referring to on "depending when that will be
released". 2.0 has already had 2 beta releases. I have been targeting doing a
release about every 3 weeks so we are due for another beta. If you could create
a Jira for this I'd appreciate it.
Ralph
On Oct 30, 2012, at 2:
https://issues.apache.org/bugzilla/show_bug.cgi?id=54078
Priority: P2
Bug ID: 54078
Assignee: log4j-dev@logging.apache.org
Summary: FlashbackAppender: new appender for lost events
Severity: enhancement
Classification: Unclassified
2012/10/30 Ralph Goers :
> I'm not sure what you are referring to on "depending when that will be
> released". 2.0 has already had 2 beta releases. I have been targeting doing
> a release about every 3 weeks so we are due for another beta. If you could
> create a Jira for this I'd appreciate i
Olivier Lamy (*$^¨%`£) created LOG4J2-105:
-
Summary: Change level name String
Key: LOG4J2-105
URL: https://issues.apache.org/jira/browse/LOG4J2-105
Project: Log4j 2
Issue Type: Bug
This brings up the larger topic of i18n.
Should we have a message properties file where folks can say "Level.WARN =
WARNING"?
Eventually, if desired, other messages can be added.
Gary
On Tue, Oct 30, 2012 at 5:16 PM, Ralph Goers wrote:
> Ahh. Good question.
>
> I was looking at LevelPatternConv
[
https://issues.apache.org/jira/browse/LOG4J2-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joern Huxhorn closed LOG4J2-85.
---
Fixed, thanks!
> Replace ThreadContext.push(String msg) with push(String msg, Object args
This is actually a sore point with me. It is my opinion that l10n doesn't
belong in the logging framework itself. That should be done in the UI where the
user is viewing the messages. If you are going to do that then you should log a
Message with a Message Id and the parameters and the entire
OK, well, that a fine POV to have. It would be nice to document that.
If we use the MVC metaphore, the log data (in a file for example) is the
model.
So let's say I do my own Logger wrapper that does l10n, I still get the log
levels in English.
What I was referring to is to l10n Log4J2 itself, b
I could certainly document that as an option, but I only have one opinion and a
successful community needs more than that. If others want more I18n support
then we will add it.
FWIW, with my suggestion a UI could treat the Level passed in the LogEvent as
the key into a resource bundle, so could
[
https://issues.apache.org/jira/browse/LOG4J2-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487574#comment-13487574
]
Evgeny commented on LOG4J2-104:
---
Ralph,
I think I did not explain myself right - I just swi
19 matches
Mail list logo
