[
https://issues.apache.org/jira/browse/STORM-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bipin Prasad resolved STORM-3829.
---------------------------------
Resolution: Fixed
> Remove log4j version 1 (1.2.17) from storm-core
> -----------------------------------------------
>
> Key: STORM-3829
> URL: https://issues.apache.org/jira/browse/STORM-3829
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-core
> Affects Versions: 2.3.0
> Reporter: Bipin Prasad
> Assignee: Bipin Prasad
> Priority: Major
> Fix For: 2.4.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> storm-core/pom.xml has the following entry:
> {code:java}
> <!--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>
> {code}
> This dependency can be removed. "mvn test" goes to success. And "mvn
> dependency:tree | grep log4j" shows no transitive dependency on log4j-1.2.17.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
