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

Make sure the result from QCL.getElementsWithResource(name) does not include duplicates #44352

Merged
merged 1 commit into from
Nov 7, 2024

Conversation

aloubyansky
Copy link
Member

@aloubyansky aloubyansky commented Nov 6, 2024

This fixes a case when QuarkusClassLoader.visitRuntimeResources(resourceName, visitor) visits the same classpath elements twice.

This comment was marked as resolved.

@quarkus-bot quarkus-bot bot added the area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins label Nov 6, 2024
* @param list2 second list
* @return resulting list
*/
private static List<ClassPathElement> unify(List<ClassPathElement> list1, List<ClassPathElement> list2) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor nitpick: I would prefer if this method was called deduplicate

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

joinAndDedupe? :)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👌

This comment has been minimized.

This comment has been minimized.

Copy link
Member

@gsmet gsmet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, thanks, but could you check the TCK issue is just a transient issue?

@aloubyansky
Copy link
Member Author

@ia3andy this will fix the issue in quarkus-roq

This comment has been minimized.

Copy link

quarkus-bot bot commented Nov 7, 2024

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 70e2f17.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

@gsmet gsmet merged commit 5d09f38 into quarkusio:main Nov 7, 2024
52 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.17 - main milestone Nov 7, 2024
@gsmet
Copy link
Member

gsmet commented Nov 7, 2024

Should we try to backport this? It might be a bit risky given it's class loader-related? If we do, I would only do it for 3.16.

@aloubyansky
Copy link
Member Author

I'd be fine either way. Perhaps @ia3andy would appreciate it being backported to 3.16.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins triage/backport-3.15 triage/flaky-test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants