Skip to content

Commit 31ffacb

Browse files
committed
fix: Manually move generated javadoc to docs/javadoc
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
1 parent cd38b2b commit 31ffacb

2 files changed

Lines changed: 1 addition & 2 deletions

File tree

default.nix

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -122,6 +122,7 @@ pkgs.stdenvNoCC.mkDerivation rec {
122122
if buildGitHubPages
123123
then ''
124124
mvn javadoc:javadoc
125+
mv target/reports/apidocs docs/javadoc
125126
JEKYLL_ENV=production PAGES_REPO_NWO=VariantSync/DiffDetective JEKYLL_BUILD_REVISION= PAGES_DISABLE_NETWORK=1 github-pages build
126127
rm -rf _site/target
127128
''

pom.xml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,8 +46,6 @@
4646
<artifactId>maven-javadoc-plugin</artifactId>
4747
<version>3.11.2</version>
4848
<configuration>
49-
<reportOutputDirectory>docs</reportOutputDirectory>
50-
<destDir>javadoc</destDir>
5149
<show>private</show>
5250
<quiet>true</quiet>
5351
</configuration>

0 commit comments

Comments
 (0)