[LOG4J2-736] Importing log4j bom changes scope of commons-code to "test"

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0
• Fix Version/s: 2.0.1
• Component/s: Core

Environment

Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e; 2014-06-17T21:51:42+08:00)
Maven home: /usr/local/java/apache-maven
Java version: 1.8.0, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre
Default locale: zh_CN, platform encoding: UTF-8
OS name: "mac os x", version: "10.9.4", arch: "x86_64", family: "mac"

• Assignee: Matt Sicker
• Reporter: Jerome Jia
• Created: 23/Jul/14 08:45
• Updated: 24/Jul/14 19:48
• Resolved: 24/Jul/14 03:29

Description

By importing log4j bom, as recommended on http://logging.apache.org/log4j/2.x/maven-artifacts.html#Bill_of_Material, according to my tests, at the moment commons-codec:commons-codec:jar:1.9 is affected, with its scope automatically changed to "test" when not explicitly specified (e.g. as "compile"). While the import of bom is removed, implicitly declared scope of commons-code is "compile" as expected.