You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Piotr Karwasz (Jira)" <ji...@apache.org> on 2022/10/26 18:56:00 UTC

[jira] [Updated] (LOG4J2-3581) Provide a migration tool from other APIs

     [ https://issues.apache.org/jira/browse/LOG4J2-3581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Piotr Karwasz updated LOG4J2-3581:
----------------------------------
    Description: Similarly to what was done by the Tomcat PMC for the {{javax.*}} to {{jakarta.*}} migration (cf. [Tomcat Migration Tool for Java EE software|https://tomcat.apache.org/download-migration.cgi]), it should be rather easy to provide a source and binary tool to convert libraries coded against Log4j 1.x, JCL, JUL or SLF4J to Log4j2.  (was: Similarly to what was done by the Tomcat PMC for the {{javax.\*}} to {{jakarta.\*}} migration (cf. [Tomcat Migration Tool for Java EE software|https://tomcat.apache.org/download-migration.cgi]), it should be rather easy to provide a source and binary tool to convert libraries coded against Log4j 1.x to Log4j2.)

> Provide a migration tool from other APIs
> ----------------------------------------
>
>                 Key: LOG4J2-3581
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3581
>             Project: Log4j 2
>          Issue Type: New Feature
>            Reporter: Piotr Karwasz
>            Assignee: Piotr Karwasz
>            Priority: Major
>
> Similarly to what was done by the Tomcat PMC for the {{javax.*}} to {{jakarta.*}} migration (cf. [Tomcat Migration Tool for Java EE software|https://tomcat.apache.org/download-migration.cgi]), it should be rather easy to provide a source and binary tool to convert libraries coded against Log4j 1.x, JCL, JUL or SLF4J to Log4j2.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)