Vasyl Danyliuk created MNG-7066:
-----------------------------------
Summary: Dependency resolution in multimodule project
Key: MNG-7066
URL: https://issues.apache.org/jira/browse/MNG-7066
Project: Maven
Issue Type: Bug
Components: Dependencies, POM
Affects Versions: 3.6.3
Reporter: Vasyl Danyliuk
Attachments: maven-test.zip
I have a bunch of modules under parent pom. In the parent pom, there is a
dependency management section that defines the 2.12.0 version of the Jackson
library. However, in one of the modules (Module One), I need to downgrade the
version to 2.10.5 due to compatibility issues. For this module, it works well.
There is a second module(Module Two) that has a dependency on Module One. And
for this dependency maven resolves the version of Jackson to 2.12.0. But Module
Two actually doesn't declare a dependency on Jackson at all, just dependency on
Module One. In the end, I'm getting compatibility issues here.
It can be resolved by explicitly specifying a dependency on Jackson 2.10.5 in
Module Two, but it still looks like a bug.
I've created a very small project to demonstrate the problem. You can check out
it here [https://github.com/DrBAXA/maven-test] or just download the attached
archive.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
