How to use javadoc:aggregate properly in multi-module maven project? -


This is my parent pom.xml file (part of it) a multi-module project In:

... & Lt; / Plugin & gt; & Lt; / Plugins & gt; & Lt; / Create & gt; ...

This plugin has been inherited in all sub-modules and I do not think this is the right approach. When I am running mvn javadoc: aggregate , the documentation is generated in target / site / apidoc , but the log is filled with warnings:

  ... [Warning] Removal: To prevent total recurring charge from forked life cycle. ...  

What am I doing?

You need to enable aggregation for this plugin:

 < Code> & lt; Plugin & gt; & Lt; ArtifactId & gt; Maven-Javadoc-plugin & lt; / ArtifactId> & Lt; Configuration & gt; & Lt; Total & gt; True & lt; / Total & gt; & Lt ;! - It enables aggretation - & gt; & Lt; / Configuration & gt; & Lt; / Plugin & gt;  

On the command line type:

  mvn javadoc: total  

edit:

Okay, I did some excavations in Jaina of the Maven Plugin and found that all javadoc plugins are annotated with mojos @gaggregator. But it seems to be problematic with Maven's aggregator, the issue for which the case has been filed

There are related bugs and some more

This is a blocker problem with Maven's aggregator For some plugins like

To summarize, you are not doing anything wrong

Just switch back to earlier versions of maven-javadoc-plugin Who does not use @groups annotation and you can not get warnings (Unless you are using some features of the Javadoc plugin, which are not available in earlier versions)

On a side note, if you run the javadoc plugin as a report @ The aggregator has been ignored.


Comments

Popular posts from this blog

Eclipse CDT variable colors in editor -

AJAX doesn't send POST query -

wpf - Custom Message Box Advice -