[ 
https://issues.apache.org/jira/browse/LOG4J2-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jerome Jia closed LOG4J2-736.
-----------------------------


Verified. Thanks.

> Importing log4j bom changes scope of commons-code to "test"
> -----------------------------------------------------------
>
>                 Key: LOG4J2-736
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-736
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0
>         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"
>            Reporter: Jerome Jia
>            Assignee: Matt Sicker
>             Fix For: 2.0.1
>
>         Attachments: pom.xml
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to