Re: Java11 and javadoc plugin

Hi Thomas, Those test sources are neither in the project we talked about earlier, nor do they have javadocs. Let's keep focused on the project you mentioned earlier. Please take a look at my explanations and the PR they resulted in. The new project (https://github.com/yagee-de/javadoc-test/

Re: Java11 and javadoc plugin

Hi Benajmin, yes I have test sources present in that directory: https://github.com/yagee-de/javadoc-test/tree/master/src/test/java/de/yagee/test Ironically „mvn javadoc:test-javadoc“ runs without any issues and

Re: Java11 and javadoc plugin

Hi Thomas, | Exit code: 2 - javadoc: error - No source files for package de.yagee.test You do not have a folder "/project/src/test/java" with any test sources! I set up an example here: https://github.com/FIUS/jvk/pull/123/files Please be aware that you still cannot create test javadocs nor

Re: Java11 and javadoc plugin

Hi Benjamin, you may have done something differently because „mvn test site“ does not work here. Could you recheck or give me a hint, what I could have done wrong? kind regards, Thomas > Am 28.10.2020 um 20:05 schrieb Benjamin Marwell : > > Hi Thomas, > > no worry, that is as easy to fix as

Re: Java11 and javadoc plugin

Hi Thomas, no worry, that is as easy to fix as the previous one. Read carefully: > Error generating maven-javadoc-plugin:3.2.0:test-aggregate-no-fork The javadoc-plugin executes "test-aggregate-no-fork". Which means: It creates javadoc for your TEST classes from src/test/java. That again

Re: Java11 and javadoc plugin

Hi, thanks for looking into it. I updated the project a bit so that you can easily switch the version with „-Djavadoc.plugin.version=3.0.1“ to see it working nice with „mvn site“ and „mvn javadoc:javadoc“. My problem is, that I don’t know how to make „site“ run again. „mvn compile site“ will

Re: Java11 and javadoc plugin

Hi Thomas, I tested your configuration and found the same issue – however, it may not be an issue after all. You configured your javadoc plugin as part of the reporting section. This usually requires the compile goal. Even if you add the jar goal to the default build->plugin section, it will