How do you resolve dependency resolution engine wasn't able to find a version warning

dronda · September 19, 2022, 4:17pm

Hi, does anyone know how to resolve the warning:
The dependency resolution engine wasn't able to find a version of module <insert module name here> which satisfied all requirements because the graph wasn't stable enough. The highest version was selected in order to stabilize selection. Features available in a stable graph like version alignment are not guaranteed in this case.

Is it because some of my dependencies rely on different versions of the same dependency or something else?

Appreciate any help with this!

Vampire · September 27, 2022, 7:23pm

Something else, depending on different versions of the same dependency is standard situation and is handled properly by Gradle.

I don’t know where this warning comes from and I have never seen it.

Can you provide an MCVE that reproduces the problem, then maybe someone can spot the problem or tell to report it as error.

musketyr · August 7, 2023, 11:59am

Hi @Vampire, I’m also trying to figure out how to prevent this warning. I don’t have reproducer but I know from where the warning comes from (and it scare me a bit). Obviously after 1000 failed attempts of module resolution, this warning is printed. I hope this helps a bit to clear what are the ways how to get rid of the warning.

github.com

gradle/gradle/blob/master/subprojects/dependency-management/src/main/java/org/gradle/api/internal/artifacts/ivyservice/resolveengine/graph/builder/ModuleResolveState.java#L445


      
                      if (maybeSkipSelectionChange(newSelected)) {
                          return;
                      }
                  }
                  changeSelection(newSelected);
              }
          }
          
          private boolean maybeSkipSelectionChange(ComponentState newSelected) {
              if (selectionChangedCounter == MAX_SELECTION_CHANGE + 1) {
                  LOGGER.warn("The dependency resolution engine wasn't able to find a version of module {} which satisfied all requirements because the graph wasn't stable enough. " +
                      "The highest version was selected in order to stabilize selection.\n" +
                      "Features available in a stable graph like version alignment are not guaranteed in this case.", id);
              }
              boolean newSelectedIsProject = false;
              if (conflictResolution == ConflictResolution.preferProjectModules) {
                  if (newSelected.getComponentId() instanceof ProjectComponentIdentifier) {
                      // Keep the project selected
                      newSelectedIsProject = true;
                  }
              }

We don’t do anything special apart from using a handful of BOMs with platform(...).

musketyr · August 7, 2023, 12:11pm

I was able to get rid of the warnings by using enforcedPlatform instead of platform in my build files.

Vampire · August 7, 2023, 2:33pm

You got me slightly wrong.
I know the code location where the warning is printed.
I just don’t know which condition causes the conflict resolution to not be able to finish at that spot, so the warning is logged.

Of course forcing versions is an option to mitigate the warning, but usually not the optimal solution. enforcedPlatform should only be used in rare edge cases and never in a library project but at most in an end product build. But even there it should seldomly use it. If it works for you, great. But if you could create an MCVE, it might make sense to open an issue with it.