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

[MRESOLVER-586] Avoid copying the type default properties map #534

Merged
merged 1 commit into from
Aug 2, 2024

Conversation

gsmet
Copy link
Contributor

@gsmet gsmet commented Jul 13, 2024

When we don't have specific properties for a DefaultArtifact, we can just reuse the type default properties map as it's readonly and immutable.
The patch contains some additional changes as I renamed the method and parameters to make them more specific so that the method wouldn't be used for things that wouldn't be safe.

When we don't have specific properties for a DefaultArtifact, we can
just reuse the type default properties map as it's readonly and
immutable.
The patch contains some additional changes as I renamed the method
and parameters to make them more specific so that the method
wouldn't be used for things that wouldn't be safe.
@gsmet
Copy link
Contributor Author

gsmet commented Jul 13, 2024

BTW, it would be awesome if it could get backported to the maven-resolver-1.9.x branch (I can do the grunt work if it's not a clean backport) as we will be stuck on Maven 3.9 for some time.

@gsmet
Copy link
Contributor Author

gsmet commented Jul 13, 2024

Backport for branch 1.9 is here: #535

@cstamas cstamas merged commit ebb47be into apache:master Aug 2, 2024
5 checks passed
@cstamas cstamas added this to the 2.0.1 milestone Aug 2, 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.

2 participants