blob: 1d68ea88d5b65ff0241b16560078b1096a321136 [file] [log] [blame]
------
Sending the output to a file
------
------
2008-09-14
------
~~ 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
Sending the output to a file
* Configuring your <<<pom.xml>>>
You can use the following configuration in your <<<pom.xml>>> to run the DOCCK
Plugin everytime the project is built and send its output to a file.
+---+
<project>
...
<build>
<plugins>
...
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-docck-plugin</artifactId>
<version>1.0</version>
<executions>
<execution>
<configuration>
<output>target/docck-results.txt</output>
</configuration>
<goals>
<goal>check</goal>
</goals>
</execution>
</executions>
</plugin>
...
</plugins>
</build>
...
</project>
+---+
* From the command-line
You can also direct the command-line execution output to a file using:
+---+
mvn docck:check -Doutput=target/docck-results.txt
+---+