Integrated DOAP Plugin With The Site Plugin

As described in DOAP In Use, you need to publish the generated DOAP file.

By default, the generated DOAP file will be deploy using the site:deploy goal in the site specified in the distributionManagement 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 site phase, like the following:

<project>
  <build>
    <plugins>
      ...
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-doap-plugin</artifactId>
        <version>3.0.0-M1</version>
        <executions>
          <execution>
            <id>site</id>
            <phase>site</phase>
            <goals>
              <goal>generate</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
      ...
    </plugins>
  </build>
</project>

Defining Meta Tag

To make the DOAP file available for all HTML files deployed on the site, you could modify the src/site/site.xml to specify a <link/> tag, i.e.:

<project>
  <body>
    <head>
      <link rel="meta" title="DOAP" href="${project.url}/doap_${project.artifactId}.rdf" type="application/rdf+xml"/>
    </head>
    ...
  </body>
</project>

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.

<project>
  <build>
    <plugins>
      ...
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-doap-plugin</artifactId>
        <version>3.0.0-M1</version>
        <configuration>
          <artifact>
            <groupId>given-artifact-groupId</groupId>
            <artifactId>given-artifact-artifactId</artifactId>
            <version>given-artifact-version</version>
          </artifact>
        </configuration>
      </plugin>
      ...
    </plugins>
  </build>
</project>