A constraint coming from a dependency management might not be taken into account if one of the dependencies is already installed

The situation is the following:

• extension A define a dependencyManagement on D-6.0
• it has a dependency on B-1.0 which itself depends on D-5.0

If B is installed first you end up in the end with D-5.0 instead of D-6.0 because XWiki notice that B is already installed and compatible.

Another problem is that then at startup if A is validated first then both A and B will end up found invalid and not loaded because they have a wrong dependency. So you get something that successfully installed but randomly fail to load (because the order in which installed extensions are loaded/validated is not really stable).