RANGER-3730: use reload4j to replace log4j-1.2
Signed-off-by: Ramesh Mani <rmani@cloudera.com>
diff --git a/knox-agent/pom.xml b/knox-agent/pom.xml
index 754c1a0..bef7575 100644
--- a/knox-agent/pom.xml
+++ b/knox-agent/pom.xml
@@ -168,9 +168,9 @@
</exclusions>
</dependency>
<dependency>
- <groupId>log4j</groupId>
- <artifactId>log4j</artifactId>
- <version>${log4j.version}</version>
+ <groupId>ch.qos.reload4j</groupId>
+ <artifactId>reload4j</artifactId>
+ <version>${reload4j.version}</version>
<scope>test</scope>
</dependency>
<dependency>
diff --git a/pom.xml b/pom.xml
index 2b76af2..8b700d0 100644
--- a/pom.xml
+++ b/pom.xml
@@ -165,8 +165,8 @@
<libpam4j.version>1.10</libpam4j.version>
<local.lib.dir>${project.basedir}/../lib/local</local.lib.dir>
<logback.version>1.2.10</logback.version>
- <log4j.version>1.2.17</log4j.version>
- <log4j2.version>2.17.1</log4j2.version>
+ <reload4j.version>1.2.19</reload4j.version>
+ <log4j2.version>2.17.2</log4j2.version>
<maven.exec.plugin.version>1.6.0</maven.exec.plugin.version>
<maven.pmd.plugin.version>3.7</maven.pmd.plugin.version>
<metrics.core.version>3.0.2</metrics.core.version>