jira-importer commented on issue #268: URL: https://github.com/apache/maven-build-cache-extension/issues/268#issuecomment-2955434107
**[Patrik Dudits](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pdudits)** commented > TBH this is the simple (and natural) solution for this. I agree that that's simple and obvious solution. > Maven is always based on gav so why not here as well > Because then it is not possible to utilize cache to improve natural Maven release flow, which has always been bit wasteful. Especially since my project is bit on the larger side, and has quite long integration test phase. Let's compare the current and future situation: |Action|Cache without version|Cache with version| |:---|:---|:---| |1.0-SNAPSHOT, release:prepare|Cache utilized|version changes during prepare, no cache, Full 1h build| |1.0, release:perform|Full 1h build, because I turn off cache for release builds|Full Build| |1.1-SNAPSHOT, regular build|Cache utilized (but misses deploy)|Full Build| So with version being part of has I will get 2 extra full builds, going from 1 hour to 3 hours build time. That's why the proposed solution doesn't make me happy, even if it is appropriate. I'd rather have it optional (but turned on by default). There are some other cases when I would still welcome reconcilation expression. One of them would be that I want to rebuild docker image whenever base image changes. I can run a script before the build to extract current tag of base images and export them in environment. I would then want this environment value to drive whether I want to execute docker:build. -- 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]
