logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerome Jia (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (LOG4J2-736) Importing log4j bom changes scope of commons-code to "test"
Date Wed, 23 Jul 2014 08:59:38 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14071515#comment-14071515
] 

Jerome Jia edited comment on LOG4J2-736 at 7/23/14 8:57 AM:
------------------------------------------------------------

A very simple pom to validate the problem. Check the output of {{mvn dependency:tree}} .

I understand merely running something like {{dependency:tree}} or {{dependency:list}} may
seem quite reckless but it accords with my actual problem running other goals/phases just
as expected.

Moreover, importing the bom only affects commons-codec for me, all my other dependencies,
e.g. various Spring artifacts, bouncycastle for jdk1.5 and above, javaee 7 API, either within
or outside "dependencyManagement", all resolve correctly. Feel free to also test these out
with the simple pom, as I'm not quite sure if this is an actual bug or some usage problem
of mine.


was (Author: iusr):
A very simple pom to validate the problem. Check the output of {{mvn dependency:tree}} .

(I understand merely running something like {{dependency:tree}} or {{dependency:list}} may
seem quite reckless but it accords with my actual problem running other goals/phases just
as expected)

> 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
>         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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message