[
https://issues.apache.org/jira/browse/LOG4J2-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17493661#comment-17493661
]
Janardhan Naidu commented on LOG4J2-3388:
-----------------------------------------
HI Team,
for the custom log level issue which I shared in above comments, I think code
changes are required in log4j side. I just created a pull request please
review and merge it . and let me know in which version we can expect the
changes.
[https://github.com/apache/logging-log4j2/pull/758/files]
Thanks
Janardhan
> 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)
