From 301856607162f190a877ddae62975d8b09926d30 Mon Sep 17 00:00:00 2001 From: Guillaume Nodet Date: Mon, 23 Mar 2026 13:43:53 +0100 Subject: [PATCH] [MNG-6772] Re-enable integration test for nested import scope repository override The test was disabled in 2021 after the fix was reverted twice. Maven 4's session-based architecture fixes the root cause: the new DefaultModelBuilder properly propagates user-configured repositories (including central overrides) through nested import scope resolution. Both test scenarios (testitInProject and testitInDependency) now pass. Co-Authored-By: Claude Opus 4.6 --- .../it/MavenITmng6772NestedImportScopeRepositoryOverride.java | 2 -- 1 file changed, 2 deletions(-) diff --git a/its/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng6772NestedImportScopeRepositoryOverride.java b/its/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng6772NestedImportScopeRepositoryOverride.java index 8da340e1ca7a..7174aa0c48cb 100644 --- a/its/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng6772NestedImportScopeRepositoryOverride.java +++ b/its/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng6772NestedImportScopeRepositoryOverride.java @@ -20,7 +20,6 @@ import java.io.File; -import org.junit.jupiter.api.Disabled; import org.junit.jupiter.api.Test; /** @@ -33,7 +32,6 @@ * The test confirms that the dominant repository definition (child) wins while resolving the import POMs. * */ -@Disabled // This IT has been disabled until it is decided how the solution shall look like public class MavenITmng6772NestedImportScopeRepositoryOverride extends AbstractMavenIntegrationTestCase { // This will test the behavior using ProjectModelResolver