------ Aggregating Javadocs for Multi-Projects ------ Maria Odea Ching Vincent Siveton ------ 2009-08-04 ------ ~~ Licensed to the Apache Software Foundation (ASF) under one ~~ or more contributor license agreements. See the NOTICE file ~~ distributed with this work for additional information ~~ regarding copyright ownership. The ASF licenses this file ~~ to you under the Apache License, Version 2.0 (the ~~ "License"); you may not use this file except in compliance ~~ with the License. You may obtain a copy of the License at ~~ ~~ http://www.apache.org/licenses/LICENSE-2.0 ~~ ~~ Unless required by applicable law or agreed to in writing, ~~ software distributed under the License is distributed on an ~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY ~~ KIND, either express or implied. See the License for the ~~ specific language governing permissions and limitations ~~ under the License. ~~ NOTE: For help with the syntax of this file, see: ~~ http://maven.apache.org/doxia/references/apt-format.html Aggregating Javadocs For Multi-Projects For example, consider the following directory structure: +-----+ Project |-- pom.xml |-- Module1 | `-- pom.xml |-- Module2 | `-- pom.xml `-- Module3 `-- pom.xml +-----+ * Using The \ Parameter (<>) <>: {{{../javadoc-mojo.html#aggregate}\}} parameter is <> since 2.5. Please use the <<>> goal instead of. The {{{../javadoc-mojo.html#aggregate}\}} parameter can be used to generate javadocs for multi-module projects. It gives the option to generate one javadoc report for the entire project (all modules) or generate one javadoc report for each module. When you execute javadoc:javadoc from Project directory with aggregate set to <>, a javadoc report will be created in the target directory of Project with all the javadocs of Project's modules included. If aggregate is set to <> (default), a javadoc report for Module1 will be generated in the target directory of Module1, a javadoc report for Module2 will be generated in the target directory of Module2, and a javadoc report for Module3 will be generated in the target directory of Module3. +-----+ ... (or ) org.apache.maven.plugins maven-javadoc-plugin ${project.version} ... true ... ... (or ) ... +-----+ * Using The <<>> Goals The {{{../javadoc-mojo.html#aggregate}\}} parameter doesn't include generate source directories defined using the {{{http://mojo.codehaus.org/build-helper-maven-plugin/add-source-mojo.html}build-helper:add-source}}. In this case, you need to use the <<>> goal and <<>> goals. You could define these goals in the \ element (using the \ tag) or \ element (using the \ tag) as shown below. For more information, refer to the {{{./selective-javadocs-report.html}Selective Javadocs Reports page}}. +-----+ ... org.apache.maven.plugins maven-javadoc-plugin ${project.version} ... aggregate aggregate site ... ... ... ... +-----+ +-----+ ... org.apache.maven.plugins maven-javadoc-plugin ${project.version} ... non-aggregate ... javadoc aggregate ... aggregate ... ... ... +-----+ The Javadoc plugin contains several <<>> goals to be use with an aggregator project. Here is the full list of all <<>> goals: * {{{../aggregate-mojo.html}javadoc:aggregate}} to generate the Javadoc files. * {{{../test-aggregate-mojo.html}javadoc:test-aggregate}} to generate the test Javadoc files. * {{{../aggregate-jar-mojo.html}javadoc:aggregate-jar}} to create an archive file of the Javadoc files. * {{{../test-aggregate-jar-mojo.html}javadoc:test-aggregate-jar}} to create an archive file of the test Javadoc files. []