slachiewicz opened a new issue, #537: URL: https://github.com/apache/maven-build-cache-extension/issues/537
### New feature, improvement proposal Integration tests whose reference project sets no `<location>` in `.mvn/maven-build-cache-config.xml` use the extension's default cache directory `~/.m2/build-cache/`. `IntegrationTestExtension` only clears `target/build-cache/` before each test, so those tests share state with every earlier run on the same machine and with any concurrent run of the suite. Observed on 2026-09-21 while verifying #536: with two `mvn verify -Prun-its` runs active at once, `IncrementalRestoreTest.simple` failed with `Text not found in log: ... restored partially. Highest cached goal: verify, requested: install` and `Issue87Test.simple` with `expected: <0> but was: <1>`. Both pass when `~/.m2/build-cache` is removed and the suite runs alone. The projects involved are `src/test/projects/mbuildcache-incremental` and `mbuildcache-87`, neither of which pins a location; `ReferenceProjectBootstrap` already passes `-Dmaven.build.cache.location=<parentDir>/target/build-cache` for the reference projects, so most of the suite is isolated. Proposal: have `IntegrationTestExtension` pass `-Dmaven.build.cache.location=` under the test's own `target/` for every project it runs, unless the test opts out, so the ITs never touch `~/.m2/build-cache`. Fresh CI runners hide this today; developer machines do not. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
