Describe your environment.
Component - maesdk Android build
Build: Gradle 9.5 with the configuration cache enabled (org.gradle.configuration-cache=true); Android Gradle Plugin 9.3.0; JDK 17
OS: Windows CI agents
Steps to reproduce.
Turn on - org.gradle.configuration-cache=true
On Windows - gradlew :maesdk:assembleRelease --configuration-cache
What is the expected behavior?
Configuring the maesdk project starts no external process, so Gradle stores the configuration cache with no problems and reuses the entry on subsequent runs.
What is the actual behavior?
Gradle reports a config cache problem invalidating the whole configuration cache every time.
1 problem was found storing the configuration cache.
- Plugin 'net.linguica.maven-settings': external process started 'cmd.exe /c set'
Additional context.
net.linguica.maven-settings uses the Maven settings builder, which via Plexus CommandLineUtils.getSystemEnvVars() shells out to cmd.exe /c set (Windows).
Gradle's configuration cache disallows starting external processes during configuration unless they go through ProviderFactory.exec() / ExecOperations:
https://docs.gradle.org/9.5.0/userguide/configuration_cache_requirements.html#config_cache:requirements:external_processes
The package had it's last release 11 years ago, and has been unmaintained since 2018. I believe we should drop it, or substitute it for a more modern package which supports latest gradle features.
Describe your environment.
Component - maesdk Android build
Build: Gradle 9.5 with the configuration cache enabled (org.gradle.configuration-cache=true); Android Gradle Plugin 9.3.0; JDK 17
OS: Windows CI agents
Steps to reproduce.
Turn on - org.gradle.configuration-cache=true
On Windows -
gradlew :maesdk:assembleRelease --configuration-cacheWhat is the expected behavior?
Configuring the maesdk project starts no external process, so Gradle stores the configuration cache with no problems and reuses the entry on subsequent runs.
What is the actual behavior?
Gradle reports a config cache problem invalidating the whole configuration cache every time.
Additional context.
net.linguica.maven-settings uses the Maven settings builder, which via Plexus CommandLineUtils.getSystemEnvVars() shells out to cmd.exe /c set (Windows).
Gradle's configuration cache disallows starting external processes during configuration unless they go through ProviderFactory.exec() / ExecOperations:
https://docs.gradle.org/9.5.0/userguide/configuration_cache_requirements.html#config_cache:requirements:external_processes
The package had it's last release 11 years ago, and has been unmaintained since 2018. I believe we should drop it, or substitute it for a more modern package which supports latest gradle features.