this fixes the use case targetted by the issue, but causes other ones:
- Maven 3 depdendency graph
- MavenRepositorySystemSession.java in maven-aether-provider
- Aether : see aether-demo particularly, since it show a direct use of Aether+maven-aether-provider to do a resolution
We should probably create a unit test in maven-aether-provider with aether-demo code to work on Maven conflict resolution enhancements: define the expected resolution and check that it works as expected.