davsclaus opened a new pull request, #27546:
URL: https://github.com/apache/camel/pull/27546
## Summary
The Develocity Maven extension's **local** build cache is currently enabled
for every build outside GitHub Actions (`#{isFalse(env['GITHUB_ACTIONS'])}`). A
cached goal is replayed instead of run, so a local `mvn verify` can print
`Loaded from the build cache` for the Failsafe goals and report a module as
tested without running its integration tests again. The cache only looks at
Maven-declared inputs, so changes outside them (such as container state) do not
invalidate it, and `mvn clean` does not bypass it. This has hidden genuinely
failing ITs locally before.
This makes the local cache opt-in, the same change Camel Quarkus made in
apache/camel-quarkus#8936:
- `.mvn/develocity.xml`: the local cache is enabled only when
`DEVELOCITY_LOCAL_CACHE_ENABLED=true`. CI already ran with it disabled, and the
remote cache stays disabled, so CI is unaffected.
- `docs/main/modules/contributing/pages/building.adoc`: the existing note
now describes the cache as opt-in, explains why it is off by default, and shows
how to enable it.
Contributors who want faster incremental builds can opt in with:
```bash
export DEVELOCITY_LOCAL_CACHE_ENABLED=true
```
## Test plan
- `mvn -N validate` succeeds with and without
`DEVELOCITY_LOCAL_CACHE_ENABLED=true`, so the extension parses the new
expression.
_Claude Code on behalf of davsclaus_
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
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]
