| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Closes #990 Maven build extensions declared in `.mvn/extensions.xml` can introduce additional plugin dependencies (e.g. lifecycle participants, custom packaging types). Including this file in the cache key hash ensures that changes to extensions — which affect what plugin JARs Maven downloads — properly invalidate the cache, preventing stale caches from missing newly-required plugin dependencies. Changes: - src/cache.ts: add `**/.mvn/extensions.xml` to Maven pattern array - __tests__/cache.test.ts: update pattern expectations; add new test - README.md: document the new file in the Maven cache key hash list
There was a problem hiding this comment.
This PR updates the Maven dependency cache key inputs so that changes to .mvn/extensions.xml (Maven build extensions) invalidate the cache, preventing restores of stale ~/.m2/repository content when extensions change.
Changes:
| File | Description |
|---|---|
| src/cache.ts | Adds **/.mvn/extensions.xml to Maven cache key hashing patterns. |
| README.md | Documents **/.mvn/extensions.xml as part of the Maven cache key hash inputs. |
| __tests__/cache.test.ts | Updates Maven pattern expectations and adds a test for extensions.xml as the only matching file. |
| dist/setup/index.js | Regenerated bundle includes Maven pattern update, but also includes large unrelated bundled-dependency changes. |
| dist/cleanup/index.js | Regenerated bundle includes Maven pattern update, but also includes large unrelated bundled-dependency changes. |
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Sorry, something went wrong.
* Initial plan * feat: add .mvn/extensions.xml to Maven cache key pattern Closes actions#990 Maven build extensions declared in `.mvn/extensions.xml` can introduce additional plugin dependencies (e.g. lifecycle participants, custom packaging types). Including this file in the cache key hash ensures that changes to extensions — which affect what plugin JARs Maven downloads — properly invalidate the cache, preventing stale caches from missing newly-required plugin dependencies. Changes: - src/cache.ts: add `**/.mvn/extensions.xml` to Maven pattern array - __tests__/cache.test.ts: update pattern expectations; add new test - README.md: document the new file in the Maven cache key hash list * test: update maven cache error test name for extensions.xml --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: Bruno Borges <brborges@microsoft.com> (cherry picked from commit 2a07c83)
| Back | FazBrowse Home | New Git URL |
Description:
Maven build extensions declared in .mvn/extensions.xml (lifecycle participants, custom packaging types, etc.) introduce additional plugin JARs that Maven downloads at build time. These were invisible to the cache key, so changes to extensions would hit the same cache key and restore a stale/incomplete ~/.m2/repository, causing repeated plugin dependency downloads.
Changes:
The Maven cache key hash is now based on:
Related issue:
#990
Check list: