 ------
 Using Alternative Output Directory
 ------
 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

Using Alternative Output Directory

 To run the Javadocs reports in an other output directory, you need to configure Javadoc Plugin as follow:

+-----+
<project>
  ...
  <reporting>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-javadoc-plugin</artifactId>
        <version>${project.version}</version>
        <configuration>
          <reportOutputDirectory>\${project.build.directory}/myoutput</reportOutputDirectory>
          ...
        </configuration>
      </plugin>
      ...
    </plugins>
  </reporting>
  ...
</project>
+-----+

  Running <<<mvn javadoc:javadoc>>> will output the Javadoc in the
  <<<$\{project.build.directory\}/myoutput/apidocs>>> instead of the default directory, i.e.
  <<<$\{project.build.directory\}/reports/apidocs>>>.

 <<Note>>: Running <<<mvn site>>> will automatically use the <<<$\{project.reporting.outputDirectory\}>>>
 directory and in this case, <<<\<reportOutputDirectory /\>>>> has no effect.
