Fix duplicate maven-source-plugin execution in docker-snapshot profile#173
Merged
Conversation
Co-authored-by: jwijgerd <914840+jwijgerd@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix duplicate artifacts error in docker-snapshot workflow
Fix duplicate maven-source-plugin execution in docker-snapshot profile
Nov 16, 2025
jwijgerd
marked this pull request as ready for review
November 16, 2025 15:43
jwijgerd
approved these changes
Nov 16, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The docker-snapshot workflow failed with "We have duplicated artifacts attached" when running
mvn install spring-boot:build-image. Thespring-boot:build-imagegoal internally triggers the package phase, causing maven-source-plugin to execute twice—once during install and again during the re-executed package phase.Changes
docker-snapshotprofile by setting phase tononeRegular builds and other profiles remain unaffected—source JARs are still generated for Maven deployments.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.