Currently the dependencyTree detects conflicts by just comparing webpackageIds of artifacts with same artifactId. This can leeds to false positive conflict detections. The conflict detection needs to support two different types of conflicts:
version conflicts
Two artifacts are in version conflict state if
the artifactId is identical
the webpackage name and groupId (if available) is identical
the version string is not identical
naming conflicts
Two artifacts are in naming conflict state if
the artifactId is identical
the webpacakge name and groupId (if available) are not identical
the version string in that case doesn't care
Tasks:
[x] Enable dependencyTree to detect both types of those conflicts
[x] Extend dependencyTree to internally store two lists of conflicted nodes based on their type of
conflict
Currently the dependencyTree detects conflicts by just comparing webpackageIds of artifacts with same artifactId. This can leeds to false positive conflict detections. The conflict detection needs to support two different types of conflicts:
Tasks:
dependencyTree
to detect both types of those conflictsdependencyTree
to internally store two lists of conflicted nodes based on their type of conflict