CMS Application - Dependencies - Missing dependencies - Default dependency is removed when setting as current version

A version shows a default dependency between two technologies (between the Cold Fusion Universal analyzer and PL/SQL in the example below) 

But when setting as current version a new version, the default dependency is removed 

Below is the step-by-step scenario leading to the problem:

1. Deliver one version of code.
2. Add new custom dependencies.
3. Deliver a new version of code and set as current version.
4. Notice that the default dependency no longer exists.

The impact of the problem on the analysis or the dashboard is:
No impact

There is no fix for the problem, this is normal behavior.

It is fully normal that this dependency is removed : it is a default dependency, which is less specific than the custom dependencies already specified explicitly. If they were kept, they would effectively negate the effect of the user config present above. The dependency is therefore removed when the new version is set as current version.