Conflicting relationships between different language versions of the same package name are not recognized.

[Tiakon]

Describe the bug

A dependency compiled in different language versions of the same package name cannot be identified as a conflicting dependency.

To Reproduce Steps to reproduce the behavior:

The project dependency structure is as follows:

project1

• project2
• json4s-scalap_2.13:3.6.6

project2

• json4s-scalap_2.11:3.7.0-M11

Expected behavior In this case, I understand that json4s-scalap_2.13:3.6.6 and json4s-scalap_2.11:3.7.0-M11 should be identified as conflicting dependencies, but this is not the case.

[krasa]

That would be tough. Isn't scala-library conflict enough?

[Tiakon]

@krasa This is different from the project dependencies I showed. In the project dependencies I showed, the conflict relationships are not shown. It's hard, but it does happen.

What I mean is that the conflict relationship of the scala class library is not displayed in the conflict option. Only visible across all dependencies, this can easily be overlooked.

[krasa]

but in the end, you still see that scala-library is conflicting and all those libraries in the right column, yes?

[Tiakon]

Yes, so I rely too much on plug-ins. 😂 😂 😂