[
https://issues.apache.org/jira/browse/LOG4J2-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17499675#comment-17499675
]
Ralph Goers commented on LOG4J2-3419:
-------------------------------------
You could modify your constructor to do
{code:java}
private Level(int paramInt1, String paramString, int paramInt2)
{
super(paramInt1, paramString, paramInt2);
org.apache.logging.log4j.Level.forName(paaramString), paramInt1);
} {code}
I should point out though that in Log4j 1 a value of 13000 would be between
DEBUG and INFO. In Log4j 2 that value would be more limiting than TRACE. To
solve this you would need to create an adjustLevel method that calculates the
Log4j 2 level based on the Log4j 1 level. So you might equate 13000 to DEBUG +
3000. In Log4j 2 you would then do StandardLevel.DEBUG - (3000 / 100) which
would result in a value or 470.
> Unable to create custom logging level using log4j 2 Bridge API
> --------------------------------------------------------------
>
> Key: LOG4J2-3419
> URL: https://issues.apache.org/jira/browse/LOG4J2-3419
> Project: Log4j 2
> Issue Type: Bug
> Components: Log4j 1.2 bridge
> Affects Versions: 2.17.1
> Environment: Using log4j 2 bridge API: log4j-1.2-api-2.17.1.jar
> Reporter: Ragini Gawande
> Priority: Blocker
>
> Unable to create custom logging level using log4j 2 Bridge API
> Following did not create a custom logging level
> *public static final int FINE_INT = 13000;*
> *public static final Level FINE = new Level(FINE_INT, "FINE", 7);*
>
> Using FINE logging level is considered to be DEBUG level by default while
> printing it
> *Adding log:*
> log.log({*}Level.FINE{*},"PRINT: Level.FINE log");
>
> *Expected log printed:*
> 2022-02-25 15:50:09,208 Main[6788] :main: example.com.Test *FINE* - PRINT:
> Level.FINE log
>
> *Actual log printed:*
> 2022-02-25 15:50:09,208 Main[6788] :main: example.com.Test *DEBUG* - PRINT:
> Level.FINE log
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
