Fix javadoc deployment #166
Merged
Conversation
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
The dependency update of the maven-javadoc-plugin in afd65e1 removed the possibility to define an alternative output directory for the generated javadoc which resulted in a warning that I missed until now. This regression was intentional and is declared as won't fix by upstream. See apache/maven-javadoc-plugin#1194
pmbittner
approved these changes
Jun 13, 2025
pmbittner
added
bug
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.
The dependency update of the maven-javadoc-plugin in afd65e1 removed the possibility to define an alternative output directory for the generated javadoc which resulted in a warning that I missed until now. This regression was intentional and is declared as won't fix by upstream. See apache/maven-javadoc-plugin#1194
Hence, we need to move the javadoc directory manually to include it in the correct location in the GitHub Pages.
This is a blocker for #157.