To solve dependencies you can exclude or replace the dependency which is causing the conflict, as follows:
Using the TAG API
Let's suppose that the third-party-lib@1.0/awesome-lib-util dependency is causing the conflict. As mentioned above, on way to solve this issue is by excluding this dependency, to aim that you should use the cubx-dependency-excludes and the cubx-dependency-exclude tags as follows:
Excluding the dependency
...
<demo-component cubx-webpackage-id="demo-package@1.0">
<cubx-dependency-excludes>
<cubx-dependency-exclude
artifact-id="awesome-lib-util"
webpackage-id="third-party-lib@1.0">
</cubx-dependency-exclude>
</cubx-dependency-excludes>
</demo-component>
...
Another approach is to replace the dependency, to aim that you should exclude i as above, and include the desired dependency using the cubx-dependencies and the cubx-dependency tags as follows:
Replacing the dependency
...
<demo-component cubx-webpackage-id="demo-package@1.0">
<cubx-dependencies>
<cubx-dependency
webpackage-id="third-party-lib@2.0"
artifact-id="awesome-lib-util">
</cubx-dependency>
</cubx-dependencies>
<cubx-dependency-excludes>
<cubx-dependency-exclude
webpackage-id="third-party-lib@1.0"
artifact-id="awesome-lib-util">
</cubx-dependency-exclude>
</cubx-dependency-excludes>
</demo-component>
...