Skip to content

Fix javadoc deployment - #166

Merged
pmbittner merged 1 commit into
developfrom
fix-javadoc-deployment
Jun 13, 2025
Merged

Fix javadoc deployment#166
pmbittner merged 1 commit into
developfrom
fix-javadoc-deployment

Conversation

@ibbem

Copy link
Copy Markdown
Collaborator

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.

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
@pmbittnerpmbittner added bug Something isn't working dependencies Pull requests that update a dependency file bm_work ibbem is paid for working on this labels Jun 13, 2025
@pmbittner
pmbittner merged commit e73e1ce into developJun 13, 2025
@ibbem
ibbem deleted the fix-javadoc-deployment branch June 13, 2025 14:09
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bm_workibbem is paid for working on thisbugSomething isn't workingdependenciesPull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@ibbem@pmbittner