Bug in the mediation of transitive dependencies

Running version v4.2.183.4139.1 (as reported by IntelliJ Idea) of this plugin

THERE SEEMS TO BE A PROBLEM (AS I UNDERSTAND IT) WITH THE TRANSITIVE DEPENDENCIES LIST/TREE WHEN COMPARED TO THE SPECIFICATION

Dependency mediation - this determines what version of an artifact will be chosen when multiple versions are encountered as dependencies. Maven picks the “nearest definition”. That is, it uses the version of the closest dependency to your project in the tree of dependencies. You can always guarantee a version by declaring it explicitly in your project’s POM. Note that if two dependency versions are at the same depth in the dependency tree, the first declaration wins. “nearest definition” means that the version used will be the closest one to your project in the tree of dependencies. For example, if dependencies for A, B, and C are defined as A -> B -> C -> D 2.0 and A -> E -> D 1.0, then D 1.0 will be used when building A because the path from A to D through E is shorter. You could explicitly add a dependency to D 2.0 in A to force the use of D 2.0.

EXAMPLE

I have the following maven projects (actual names obfuscated):

A 12.0.1

A 13.0.0

A 13.2.0

B 12.0.1
  -> A 12.0.1

B 12.0.2
  -> A 13.0.0

C 8.2.0
  -> A 13.2.0
  -> B 12.0.2

D 0.7.1
  -> A 13.0.0
  -> C 12.0.1

When E is defined as

E 0.9.3
  -> A 13.2.0
  -> C 8.2.0
  -> D 0.7.1

transitive dependencies in the dependency tree/list is wrong

E 0.9.3
  -> A 13.2.0
  -> C 8.2.0
     -> A 13.2.0
     -> B 12.0.2
          -> A 13.0.0 (omitted for conflict with 13.2.0) -- CORRECT
  -> D 0.7.1
    -> A 13.2.0 -- WRONG!!! SHOULD BE 13.0.0 and omitted for conflict with 13.2.0
    -> B 12.0.1 (omitted for conflict with 12.0.2)  -- CORRECT

When E is defined as

E 0.9.3
  -> A 13.2.0
  -> D 0.7.1
  -> C 8.2.0

transitive dependencies in the dependency tree/list is correct

E 0.9.3
  -> A 13.2.0
  -> D 0.7.1
    -> A 13.0.0 (omitted for conflict with 13.2.0) -- CORRECT
    -> B 12.0.1 -- CORRECT 
          -> A 12.0.1 (omitted for conflict with 13.2.0) -- CORRECT
  -> C 8.2.0
     -> A 13.2.0
     -> B 12.0.2 (omitted for conflict with 12.0.1) -- CORRECT

Why this bothers me is that it failed to report a dependency conflict when it was supposed to!

[krasa]

I released a new version with a fix.

[krasa]

@ruwanka probably a bug, I might have done it too strict. A reproducible project would help, or you could debug it yourself