How to avoid calling javadoc more than once if creating a site?

Question

I would like to deploy an artifact together with javadoc and a Maven site. I use

clean javadoc:jar site deploy site:deploy

(the split between site and site:deploy is just to avoid the deployment of a site if deploy fails).

Now the javadoc is created twice - once in javadoc:jar and once in site. Is it possible to create it just once and use it both for the javadoc-jar in Nexus and the Maven site?

Did you try to add section to your pom, to generate javadocs as part of the site generation? — Kayvan Tehrani, Dec 14 '17 at 15:08
javadoc _is_ generated in the site build, but is not bundled into a jar (unless I also call javadoc:jar) — J Fabian Meier, Dec 14 '17 at 15:18

score 5 · Accepted Answer · answered Dec 09 '17 at 11:28

5

I'm pretty sure the plugin is missing a check if the output is already generated as part of the Maven session. Would be a nice improvement to verify if the output is generated after Maven had started. (and let's add a force-parameter to enforce the creation anyway).

answered Dec 09 '17 at 11:28

Robert Scholte

11,889
2
35
44

I'm sorry, actually I don't understand your advice (or what I should try)? As we start with a `clean`, everything is created after Maven has started. – J Fabian Meier Dec 10 '17 at 11:44
It is not an advice, I'm saying that if you call 2 goals of the maven-javadoc-plugin, it will call the javadoc tool twice due to missing optimization. – Robert Scholte Dec 10 '17 at 14:37

score 1 · Answer 2 · answered Dec 15 '17 at 08:01

Possible solution that may you use is creation two different scripts for build/deploy and run them one by one:

Firstly - full build with with -Dmaven.javadoc.skip=true, that avoids you to create javadoc
Another - only run mvn javadoc:javadoc command to get actual javadoc

Also, maybe next link help you:

So, you can specify execution phase of javadoc plugin and specify reportSet.

How to avoid calling javadoc more than once if creating a site?

2 Answers2