Restore linux-aarch64 artifacts to Maven Central publish#981
Open
colleenkinross wants to merge 1 commit into
Open
Restore linux-aarch64 artifacts to Maven Central publish#981colleenkinross wants to merge 1 commit into
colleenkinross wants to merge 1 commit into
Conversation
The linux-aarch64 artifacts were dropped starting in 2.0.72 when PR netty#926 migrated from nexus-staging-maven-plugin to central-publishing-maven-plugin. Unlike other platforms which build openssl-dynamic and boringssl-static in a single Maven command, the aarch64 cross-compile requires two separate commands because only openssl-dynamic needs -DaprArmHome and -DopensslArmHome. The old plugin accepted -DaltStagingDirectory to write staging output outside of target/, so it survived the clean in the second command. The new plugin defaults to target/central-staging, which the second command's clean deletes before uploading. Fix by passing -DoutputDirectory=/root/local-staging to both publish calls, mirroring the original -DaltStagingDirectory behavior, then copying the combined output into target/central-staging for the CI upload step.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The linux-aarch64 artifacts were dropped starting in 2.0.72 when PR #926 migrated from nexus-staging-maven-plugin to central-publishing-maven-plugin.
Unlike other platforms for which we can build openssl-dynamic and boringssl-static in a single command, the aarch64 cross-compile requires two separate commands because openssl-dynamic must be built against a pre-compiled ARM version of APR and OpenSSL and boringssl-static doesn't have this dependency. The old plugin accepted -DaltStagingDirectory to write staging output outside of target/, so it survived the clean phase in the second command. The new plugin defaults to target/central-staging, which the clean phase in the second command deletes along with the rest of the root project's target/ directory.
Fix by passing -DoutputDirectory=/root/local-staging to both publish calls, mirroring the original -DaltStagingDirectory behavior, then copying the combined output into target/central-staging for the CI upload step.