[jira] [Commented] (LOG4J2-3532) Log4j 2.x is not compatible with Jansi 2.x

["Piotr Karwasz (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4J2-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552337#comment-17552337 ] 

Piotr Karwasz commented on LOG4J2-3532:
---------------------------------------

[~simonikula], personally I find the properties configuration much less readable than the XML config (actually any configuration format is more readable).

I was able to reproduce your problem by switching the {{XMLParserConfiguration}} of the most recent Xerces version as described in [Xerces Native Interface FAQ|https://xerces.apache.org/xerces2-j/faq-xni.html]. E.g. with:

{noformat}
-Dorg.apache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers.DTDConfiguration
{noformat}

You can probably fix XInclude by switching the configuration to {{XIncludeAwareParserConfiguration}}.


> Log4j 2.x is not compatible with Jansi 2.x
> ------------------------------------------
>
>                 Key: LOG4J2-3532
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3532
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Appenders, Core
>    Affects Versions: 2.15.0, 2.16.0, 2.17.1, 2.17.0, 2.17.2
>            Reporter: Joseph Choi
>            Priority: Minor
>
> Since Log4j 2.15.0, the project POM has been updated to depend on Jansi 2.x, however, the {{ConsoleAppender}} still expects the presence of the Jansi 1.x class {{{}WindowsAnsiOutputStream{}}}, which has already been removed in Jansi 2.x.
> The ANSI coloring will not work if the application bundles with Jansi 2.x.  As a workaround, the application still needs to bundle with the old Jansi 1.x library, which contradicts with the definition in the POM.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)