[
https://issues.apache.org/jira/browse/LOG4J2-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17493802#comment-17493802
]
Janardhan Naidu commented on LOG4J2-3388:
-----------------------------------------
deleted the pull request as it will cause compilation issue.
for now, it is working for me with below configuration which is slightly
different compare to how we define these properties in xml file. So need to fix
it? please have a look at it.
customLevels = VERBOSE
customLevel.VERBOSE=525
> Migration from log4j1.x to log4j2.x
> -----------------------------------
>
> Key: LOG4J2-3388
> URL: https://issues.apache.org/jira/browse/LOG4J2-3388
> Project: Log4j 2
> Issue Type: Question
> Reporter: Janardhan Naidu
> Priority: Major
>
> We are planning to upgrade log4j1.x to log4j2.x.
> So we went through the migration document:
> [https://logging.apache.org/log4j/2.x/manual/migration.html]
> in the above document, It says that (They must not access methods and classes
> internal to the Log4j 1.x implementation such as Appenders, LoggerRepository
> or Category’s callAppenders method.)
> and In our product, currently we are using log4j1.x and we are extending some
> of the log4j1.x classes like PatternParser, FileAppender etc... which were
> made final in log4j2.x so can we make use of Log4j 1.x bridge.? If yes how
> we can do that.
>
> what could be the better option to migrate log4j 1.x to log4j 2.x as we are
> making use of log4j internal classes?
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
