Browse Source
When Maven runs with -T N, all modules using the packaging profile invoke gradle-maven-plugin against the same gradleProjectDirectory (packaging/java or packaging/js), causing them to share and contend on the same .gradle/ project cache directory simultaneously. Two fixes: - Pass --project-cache-dir pointing to each module's own target/.gradle, fully isolating parallel Gradle invocations from each other. - Add maven-clean-plugin filesets to remove packaging/java/.gradle and packaging/js/.gradle on mvn clean. Gradle always writes project-level metadata to the project directory regardless of --project-cache-dir, so these would otherwise accumulate on CI agents with persistent home directories.pull/15248/head
1 changed files with 17 additions and 0 deletions
Loading…
Reference in new issue