org.apache.maven.its.plugins maven-it-plugin 0.1 it false true generate-metadata Does nothing. compile false true false false false true process-classes org.apache.maven.plugin.coreit.DMojo java per-lookup once-per-session java Does nothing. false true false false false true generate-sources org.apache.maven.plugin.coreit.AMojo java per-lookup once-per-session models java.lang.String[] false true version java.lang.String false true ${version} generate-test-metadata Does nothing. test false true false false...

        <executions>
          <execution>
            <id>plugin</id>
            <goals>
              <goal>velocity</goal>
            </goals>
            <phase>generate-sources</phase>
            <configuration>
              <velocityBasedir>${project.basedir}/../../src/mdo</velocityBasedir>
              <version>2.0.0</version>
              <models>

// I want to set up a local/remote repositories for testing but I don't want to have
// to change them when I change the layout of the repositories. So I want to generate
// the structure I want to test by using the artifact handler manager which dictates
// the layout used for a particular artifact type.

/**
 */
@Deprecated

        <executions>
          <execution>
            <id>plugin</id>
            <goals>
              <goal>velocity</goal>
            </goals>
            <phase>generate-sources</phase>
            <configuration>
              <velocityBasedir>${project.basedir}/../../src/mdo</velocityBasedir>
              <version>1.2.0</version>
              <models>

        <executions>
          <execution>
            <id>velocity-settings</id>
            <goals>
              <goal>velocity</goal>
            </goals>
            <phase>generate-sources</phase>
            <configuration>
              <version>2.0.0</version>
              <basedir>${project.basedir}/../api/maven-api-settings</basedir>

        <field>
          <name>reporting</name>
          <version>4.0.0+</version>
          <description>
            This element includes the specification of report plugins to use
            to generate the reports on the Maven-generated site.
            These reports will be run when a user executes {@code mvn site}.
            All the reports will be included in the navigation bar for browsing.
          </description>

      <fields>
        <field>
          <name>id</name>
          <required>true</required>
          <version>1.0.0</version>
          <type>String</type>
          <description>The ID of this phase, e.g., &lt;code&gt;generate-sources&lt;/code&gt;.</description>
        </field>
        <field>
          <name>executions</name>
          <version>1.0.0</version>
          <description>The goals to execute within the phase.</description>

          <models />
        </configuration>
        <executions>
          <execution>
            <!-- This step is required to generate xdoc, and does not generate java code -->
            <id>modello-site-doc</id>
            <goals>
              <goal>xdoc</goal>
            </goals>
            <phase>pre-site</phase>
            <configuration>

        // [01] clean:clean
        // [02] resources:resources
        // [03] compiler:compile
        // [04] it:generate-metadata
        // [05] resources:testResources
        // [06] compiler:testCompile
        // [07] it:generate-test-metadata
        // [08] surefire:test
        // [09] jar:jar
        // [10] install:install
        //

                        </executions>
                    </plugin>
                </plugins>
            </build>
        </profile>
        <profile>
            <id>generate-docs</id>
            <!--
            Generate the documentation artifacts. 
            Note: this profile is also required to be active for release
            builds due to the packaging requirements of the Central repo
            -->