tfactor2 commented on issue #449: URL: https://github.com/apache/maven-build-cache-extension/issues/449#issuecomment-4793253507
Follow-up verification for #498: The compile -> package/install failure mode from this issue is still possible if a compile-only cache entry records `target/classes` as the main artifact. The new PR fixes the save-side invariant instead of only working around restore: compile outputs are cached as attached output archives, and the main artifact is saved/restored only when it has a real packaged file path. Verified scenarios: - `mvn compile` cache entry still stores `target/classes`, but under `attachedArtifacts`, not as the main project artifact. - `mvn package` after a compile cache hit partially restores compile outputs, runs packaging, and saves the main artifact as the built JAR. - `mvn clean install` after a compile cache hit succeeds and saves the main artifact as the built JAR. - Legacy directory-backed main-artifact cache entries are guarded so they cannot be treated as valid package-or-later cache hits. PR: #498 The minimal reproducer zip is kept out of the source tree; it should be attached to the issue rather than committed. -- 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]
