Adam Burke created IVY-1619:
-------------------------------
Summary: Ivy provided handling incorrect, making log4j2 > 2.8.2
unusable
Key: IVY-1619
URL: https://issues.apache.org/jira/browse/IVY-1619
Project: Ivy
Issue Type: Bug
Reporter: Adam Burke
Attachments: ivy.xml, ivyout_20200910.log, ivysettings.xml
Hi team
As detailed and discussed at LOG4J2-2845, ivy will fail to download any log4j
dependency with version greater than 2.8.2, including the latest, which at time
of writing is already 2.13.3.
This looks like it is caused by problems in ivy with the "provided" keyword,
which is used for log4j's artifacts from 2.8.2 onwards.
Suggested workarounds also welcome.
Example output from my own environment and a minimal example attached. Key
error text:
{{:: resolving dependencies :: bpmqut#SPNDiscoverAB;latest}}
{{ confs: [default]}}
*{{found org.apache.logging.log4j#log4j-api;2.13.3 in maven2}}*
\{{ found org.osgi#org.osgi.core;4.3.1 in maven2}}
\{{ found org.apache.felix#org.apache.felix.framework;5.6.10 in maven2}}
{{...}}
{{==== maven2:
tried}}{{[https://repo1.maven.org/maven2/org/apache/logging/log4j/log4j-core-java9/2.13.3/log4j-core-java9-2.13.3.pom]}}{{--
artifact
org.apache.logging.log4j#log4j-core-java9;2.13.3!log4j-core-java9.zip:}}{{[https://repo1.maven.org/maven2/org/apache/logging/log4j/log4j-core-java9/2.13.3/log4j-core-java9-2.13.3.zip]}}{{====
local: tried}}{{::::::::::::::::::::::::::::::::::::::::::::::}}{{::
UNRESOLVED DEPENDENCIES
::}}{{::::::::::::::::::::::::::::::::::::::::::::::}}{{::
org.apache.logging.log4j#log4j-api-java9;2.13.3: not found}}{{::
org.apache.logging.log4j#log4j-core-java9;2.13.3: not found}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
