Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure no duplicates after pom jar unification #1269

Conversation

cerisier
Copy link

The same artifact can being depended on via pom and jar at different places in the tree. In such case, we deduplicate it so that 2 entries do not reference the same file, which will otherwise lead in symlink error because of existing file down the road.

Fixes #1267

The same artifact can being depended on via pom and jar at different
places in the tree. In such case, we deduplicate it so that 2
entries do not reference the same file, which will otherwise lead
in symlink error because of existing file down the road.
@honnix
Copy link
Contributor

honnix commented Oct 21, 2024

FWIW, #1266 also addresses the same issue.

@jin
Copy link
Collaborator

jin commented Nov 13, 2024

Thanks for this PR! I've merged #1266 as that PR came first.

@jin jin closed this Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Depending on both POM and JAR of the same maven artifact causes symlink error at artifacts pinning
3 participants