BUILD-8083 Fix javadoc publication when multiple javadocs are available#330
Merged
BUILD-8083 Fix javadoc publication when multiple javadocs are available#330
Conversation
fdeaa51 to
64db46e
Compare
64db46e to
d60d009
Compare
🤖 Pull Request summaryRefactors javadoc extraction in CI workflow to use dedicated script with testing. • Adds checkout step to javadoc-publication workflow
|
tomverin
approved these changes
Jul 28, 2025
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
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 javadoc publication workflow failed for repositories like
sonar-plugin-apithat generate multiple javadoc artifacts:sonar-plugin-api-13.0.0.3026-javadoc.jar(main API docs)sonar-plugin-api-test-fixtures-13.0.0.3026-javadoc.jar(test utilities)The existing logic
mv *javadoc.jar javadoc.zipfailed with "No such file or directory" when multiple files matched the pattern.Solution
Enhanced the javadoc extraction step with intelligent file selection:
Tested scenarios: 7/7 unit tests pass, covering single javadoc, multiple with test/fixture variants, edge cases, and error conditions. As there are no unit tests in the repo, I kept them locally