Fix validatePackageContents.ps1 failing on build-ci pipeline#2636
Open
ramsessanchez wants to merge 1 commit into
Open
Fix validatePackageContents.ps1 failing on build-ci pipeline#2636ramsessanchez wants to merge 1 commit into
ramsessanchez wants to merge 1 commit into
Conversation
Maven build does not produce .module/.module.asc files after the gradle-to-maven migration, so validatePackageContents.ps1 fails on the build-ci pipeline. Remove those from the expected files list. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Problem
The
Inspect contents of local Maven cachestep in the build-ci pipeline fails becausescripts/validatePackageContents.ps1requires.moduleand.module.ascfiles.Cause
After the gradle-to-maven migration (#2613), the build uses Maven (javadoc/source/gpg plugins), which does not produce Gradle Module Metadata (
.module/.module.asc). The script still expected them, soTest-Pathfailed and the script exited 1.Fix
Removed
.moduleand.module.ascfrom the\list. The remaining expected artifacts (jar, sources, javadoc, pom, and their.ascsignatures) are still produced by the Maven build.