The problem can be reproduced by going to any Jenkins plugin today and running mvn javadoc:javadoc with Java 8. The problem does not occur when running the same Maven command with Java 11. So one solution is to perform the release with Java 11 (as we are doing with Jenkins core today).
I suspect this may have something to do with the renaming of package-list to element-list in Java 10. I see https://javadoc.jenkins.io/element-list but https://javadoc.jenkins.io/package-list gives a 404 (Javadoc built with Java 11). In contrast, I see https://javadoc.jenkins.io/component/jenkins-test-harness/package-list but https://javadoc.jenkins.io/component/jenkins-test-harness/element-list gives a 404 (Javadoc built with Java 8). If this theory is correct, another solution might be to symlink package-list to element-list as was effectively done in gradle/gradle@5e88351dd456a5252d21f3a7ad25bff1b62a2fd2 <https://github.com/gradle/gradle/commit/5e88351dd456a5252d21f3a7ad25bff1b62a2fd2> . -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjrWQWFnDt7KkvGLxL4Y1L9_bqhNxdtvD1dORzfGHEcbvw%40mail.gmail.com.
