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

Re-implement shadow's "component" method to correctly #4129

Merged
merged 2 commits into from
Jul 5, 2023

Conversation

niloc132
Copy link
Member

@niloc132 niloc132 commented Jul 5, 2023

Does not address #4122, which would require changing shadow to use components correctly.

Fixes #4119

Does not address deephaven#4122, which would require changing shadow to use
components correctly.

Fixes deephaven#4119
@niloc132 niloc132 requested a review from devinrsmith July 5, 2023 17:54
@niloc132 niloc132 added NoDocumentationNeeded ReleaseNotesNeeded Release notes are needed build release blocker A bug/behavior that puts is below the "good enough" threshold to release. labels Jul 5, 2023
@devinrsmith devinrsmith added this to the June 2023 milestone Jul 5, 2023
@niloc132
Copy link
Member Author

niloc132 commented Jul 5, 2023

This is not an ideal fix, but it does the job. I wasn't able to get the shadow plugin to be delayed in its changes of the default pom instance so that the GenerateMavenPom task is able to write it correctly, but instead just reimplements the logic to more closely match what we expect.

A "better" fix would delay our call to project.shadow.component() until after gradle has processed the artifactId changes to all dependency projects, propagating them into their own poms, so that they can be read.

A "good" fix would be to provide a variant or a component just for the shadow. It appears that the shadow plugin attempts to do this, but doesn't really commit to it (giving us #4122).

Note that we also cannot update to shadow 8.1.1 at this time, as it requires gradle 8.

@devinrsmith
Copy link
Member

Filed #4132 for follow-up.

@niloc132
Copy link
Member Author

niloc132 commented Jul 5, 2023

Filed #4132 for follow-up.

Based on my read of the specific sources involved with this bug, this is unlikely to help.

@niloc132 niloc132 enabled auto-merge (squash) July 5, 2023 19:11
@niloc132 niloc132 merged commit ac6a1f9 into deephaven:main Jul 5, 2023
9 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Jul 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
build NoDocumentationNeeded release blocker A bug/behavior that puts is below the "good enough" threshold to release. ReleaseNotesNeeded Release notes are needed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unable to build against DHC's psk-authentication-provider
2 participants