Skip to content
New issue

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

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

Already on GitHub? # to your account

Fix resource inclusion in TCK jars #1974

Merged

Conversation

arjantijms
Copy link
Contributor

Because of including the license file, the default resource inclusion was broken. All jars files for TCKs that needed resource inclusion were broken.

This PR fixes that.

CC @alwin-joseph @anajosep @arjantijms @cesarhernandezgt @dblevins @m0mus @edbratt @gurunrao @jansupol @jgallimore @kazumura @kwsutter @LanceAndersen @bhatpmk @RohitKumarJain @shighbar @gthoman @brideck @OndroMih @dmatej
@starksm64 @scottmarlow

@arjantijms arjantijms added this to the 11.0 milestone Feb 23, 2025
@arjantijms arjantijms self-assigned this Feb 23, 2025
@arjantijms arjantijms merged commit 00b24de into jakartaee:main Feb 23, 2025
2 checks passed
@arjantijms arjantijms deleted the fix_resource_inclusion_tck_jars branch February 23, 2025 20:28
@edburns
Copy link
Contributor

edburns commented Feb 24, 2025

I take responsibility for this. My changes for #1955 caused this regression in the case where a POM did not have a <resources> element. I suspect by adding a <resources> element where none had been caused the implicit rule to include src/main/resources to no longer take effect. Sorry about that, and thanks @arjantijms for fixing it.

@arjantijms
Copy link
Contributor Author

No problem, exactly this occured to me many times before.

A good lesson is that the CI needs to run the latest version of what we stage.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants