------ Integrated DOAP Plugin in the Site Plugin ------ Vincent Siveton ------ 2010-12-16 ------ ~~ 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 Integrated DOAP Plugin With The Site Plugin As described in {{{./doap-in-use.html}DOAP In Use}}, you need to publish the generated DOAP file. By default, the generated DOAP file will be deploy using the <<<{{{http://maven.apache.org/plugins/maven-site-plugin/usage.html}site:deploy}}>>> goal in the site specified in the section of the POM. * Including DOAP In The Site Phase You could always generate the DOAP file for your project by sticking the DOAP Plugin in the <<>> phase, like the following: +-----+ ... org.apache.maven.plugins maven-doap-plugin ${project.version} site site generate ... +-----+ * Defining Meta Tag To make the DOAP file available for all HTML files deployed on the site, you could modify the <<>> to specify a \ tag, i.e.: +-----+ ... +-----+ * Generating DOAP from Another Maven Project Since 1.1, you could generate the DOAP file against another Maven Project. It could be useful, if you have a main project and a site project. +-----+ ... org.apache.maven.plugins maven-doap-plugin ${project.version} given-artifact-groupId given-artifact-artifactId given-artifact-version ... +-----+