You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@storm.apache.org by bi...@apache.org on 2022/03/04 19:11:51 UTC
[storm] branch 2.4.x-branch updated: [STORM-3829] Remove log4j 1.2.17 as a test dependency (#3450)
This is an automated email from the ASF dual-hosted git repository.
bipinprasad pushed a commit to branch 2.4.x-branch
in repository https://gitbox.apache.org/repos/asf/storm.git
The following commit(s) were added to refs/heads/2.4.x-branch by this push:
new 17de353 [STORM-3829] Remove log4j 1.2.17 as a test dependency (#3450)
17de353 is described below
commit 17de353136950b43d253d24aae2b6ff947bdbe61
Author: Bipin Prasad <bi...@yahoo.com>
AuthorDate: Fri Mar 4 09:55:54 2022 -0800
[STORM-3829] Remove log4j 1.2.17 as a test dependency (#3450)
Co-authored-by: Bipin Prasad <bp...@yahooinc.com>
---
storm-core/pom.xml | 11 -----------
1 file changed, 11 deletions(-)
diff --git a/storm-core/pom.xml b/storm-core/pom.xml
index 162abc8..f54d4e0 100644
--- a/storm-core/pom.xml
+++ b/storm-core/pom.xml
@@ -58,17 +58,6 @@
<scope>test</scope>
</dependency>
- <!--Hadoop Mini Cluster cannot use log4j2 bridge,
- Surefire has a way to exclude the conflicting log4j API jar
- from the classpath, classpathDependencyExcludes, but it didn't work in practice.
- This is here as a work around to place it at the beginning of the classpath
- even though maven does not officially support ordering of the classpath.-->
- <dependency>
- <groupId>log4j</groupId>
- <artifactId>log4j</artifactId>
- <version>1.2.17</version>
- <scope>test</scope>
- </dependency>
<!--clojure-->
<dependency>
<groupId>org.clojure</groupId>