If module participates in conflict resolution and candidates are declared by a mix of dynamic versions and static versions, then the dynamic constraints incorrectly downgrades a version.

Example:

1. Candidates of conflict resolution: foo:1.0, foo:[1.5, 1.9], foo:2.0+
2. Only foo:1.5 is available in the repository
3. Dependency resolution succeeds and selected version for foo:2.0+ is foo:1.5 which clearly does not meet the 2.0+ constraint.

Please look for a test case for this issue in the codebase (marked with @Issue).