fix: Use maven-core instead of maven-settings-builder for full resolver stack

maven-settings-builder alone is insufficient - SCC plugin also needs
DefaultServiceLocator from maven-resolver-impl, which maven-core
pulls in transitively. The plugin needs the full Maven resolver stack.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: marcingrzejszczak

producer_with_external_contracts/build.gradle

@@ -3,10 +3,10 @@ buildscript {
 		mavenCentral()
 	}
 	dependencies {
-		// Workaround: SCC 5.0.3-SNAPSHOT plugin is missing this transitive dep
-		// needed by copyContracts task for Maven settings decryption. Remove
-		// when SCC plugin fixes its dependency declarations.
-		classpath 'org.apache.maven:maven-settings-builder:3.9.6'
+		// Workaround: SCC 5.0.3-SNAPSHOT plugin is missing Maven resolver
+		// transitive deps needed by copyContracts task. Remove when SCC
+		// plugin fixes its dependency declarations.
+		classpath 'org.apache.maven:maven-core:3.9.6'
 	}
 }
 

producer_with_git/build.gradle

@@ -3,10 +3,10 @@ buildscript {
 		mavenCentral()
 	}
 	dependencies {
-		// Workaround: SCC 5.0.3-SNAPSHOT plugin is missing this transitive dep
-		// needed by copyContracts task for Maven settings decryption. Remove
-		// when SCC plugin fixes its dependency declarations.
-		classpath 'org.apache.maven:maven-settings-builder:3.9.6'
+		// Workaround: SCC 5.0.3-SNAPSHOT plugin is missing Maven resolver
+		// transitive deps needed by copyContracts task. Remove when SCC
+		// plugin fixes its dependency declarations.
+		classpath 'org.apache.maven:maven-core:3.9.6'
 	}
 }