You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitriy Pavlov (JIRA)" <ji...@apache.org> on 2018/07/23 16:41:00 UTC
[jira] [Resolved] (IGNITE-9035) Update log4j 2x version in Apache
Ignite
[ https://issues.apache.org/jira/browse/IGNITE-9035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy Pavlov resolved IGNITE-9035.
------------------------------------
Resolution: Fixed
[~SomeFire], I've also checked tests run, and all suspicisous test are rare flaky failures.
Merged to master.
Thank you for contribution!
> Update log4j 2x version in Apache Ignite
> ----------------------------------------
>
> Key: IGNITE-9035
> URL: https://issues.apache.org/jira/browse/IGNITE-9035
> Project: Ignite
> Issue Type: Improvement
> Reporter: Dmitriy Pavlov
> Assignee: Ryabov Dmitrii
> Priority: Major
> Fix For: 2.7
>
>
> It is suggested to update log4j 2x version to log4j 2.8.2 or later.
> {noformat}
> <dependency>
> <groupId>org.apache.logging.log4j</groupId>
> <artifactId>log4j</artifactId>
> <version>2.8.2</version>
> <type>pom</type>
> </dependency>
> {noformat}
> It is required to run RunAll to check all tests passed.
> Probably it is required to run release step to make sure release candidate can be prepared.
> This will affect at least ignite-log4j2, ignite-spark and probably other modules.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)