fix(ModuleManager): loosen auto-generated dependency version

getNextPatchVersion was too narrow when the base version was a snapshot. (That may be a gestalt-module bug, but it's an edge case and using MinorVersion here seems fine.)
MovingBlocks · Apr 2, 2021 · 20546f1 · 20546f1
1 parent 2f9d4af
commit 20546f1
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/engine/src/main/java/org/terasology/engine/core/module/ModuleManager.java b/engine/src/main/java/org/terasology/engine/core/module/ModuleManager.java
@@ -94,7 +94,7 @@ private void ensureModulesDependOnEngine() {
         DependencyInfo engineDep = new DependencyInfo();
         engineDep.setId(engineModule.getId());
         engineDep.setMinVersion(engineModule.getVersion());
-        engineDep.setMaxVersion(engineModule.getVersion().getNextPatchVersion());
+        engineDep.setMaxVersion(engineModule.getVersion().getNextMinorVersion());
 
         HashSet<Name> engineModules = Sets.newHashSet(engineModule.getId());
         engineModules.addAll(engineModule.getMetadata().getDependencies().stream().map(DependencyInfo::getId).collect(Collectors.toList()));