chore(deps): update dependecy groovy-xml to 4.0.6

[TomBursch]

Closes #1399

upgrades org.codehaus.groovy:groovy-xml:3.0.10 to org.apache.groovy:groovy-xml:4.0.6

[nedtwigg]

All of the Gradle tests fail, I think because the Groovy version needs to match Gradle's version. Do you have a specific need to update the Groovy? I'm happy to merge this if you figure out a way for it to not break Gradle.

[TomBursch]

Hi, thanks for the fast response! Do you have a clue what the problem could be here? I'm already running the latest gradle version (build fails for me too) and I couldn't find anything where you manually set a different gradle version.

One of our plugin dependencies also uses a later version of groovy and due to the name change some dependency conflicts arise. Mainly that two different transitive dependencies have the same capabilities.

[nedtwigg]

We test on different Gradle versions for different tests

spotless/plugin-gradle/src/test/java/com/diffplug/gradle/spotless/GradleIntegrationHarness.java

Line 111 in 9ecec25

.withGradleVersion(GradleVersionSupport.MINIMUM.version)

spotless/plugin-gradle/src/test/java/com/diffplug/gradle/spotless/GradleIntegrationHarness.java

Lines 44 to 49 in 9ecec25

	public enum GradleVersionSupport {
	JRE_11("5.0"), MINIMUM(SpotlessPlugin.MINIMUM_GRADLE),
	// technically, this API exists in 6.5, but the flags for it change in 6.6, so we build to that
	CONFIGURATION_CACHE("6.6"),
	// https://docs.gradle.org/7.5/userguide/configuration_cache.html#config_cache:stable
	STABLE_CONFIGURATION_CACHE("7.5");

I'm probably okay with bumping our minimum required Gradle to support this change because other people will have this problem eventually too.

[ben-snaize]

Been watching this fix, as it breaks parents like react-native-reanimated. Any ideas when it will go into production? We're currently have to patch it away.

[nedtwigg]

Well this is a bit embarassing, but it turns out we don't even need this dep at all anymore.

• 923d875
• chore(deps): update dependency gradle to v7.6 #1409

What happened is that we did use groovy-xnl inside of the JDT step in the past, and at some point it was refactored out but the dep wasn't removed.