vladilm opened a new pull request, #577: URL: https://github.com/apache/maven-build-cache-extension/pull/577
The Maven Build Cache Extension originally assumed that it received a module’s lifecycle executions as one batch. Maven 4’s concurrent builder invokes it separately for individual lifecycle steps. As a result, each completed step could overwrite the same cache entry. After a successful build, the entry might describe only the final test execution, with no record of compilation or resource processing. The next build rejected that incomplete entry and repeated the work. This change accumulates completed executions per project and saves the combined cache entry only after the Maven session finishes successfully. If the reactor reports an error, no new concurrent cache entries are saved. Saving at session completion is deliberate. In the tested Maven 4.0.0-rc-3 concurrent implementation, project-completion events could identify a project through the current session context rather than the project whose teardown was executing. Session completion provides a conservative boundary after all reactor work has finished. The existing smart-builder path remains unchanged. --- To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0) check one of the following: - [x] I hereby declare this contribution to be licensed under the [Apache License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0) - [x] I hereby declare that I have filed an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- 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]
