<artifactId>maven-it-plugin</artifactId>
  <version>0.1</version>
  <packaging>maven-plugin</packaging>

  <name>Maven Integration Test Plugin</name>
  <description>
    A test plugin to assist testing of Maven core.
  </description>
  <inceptionYear>2009</inceptionYear>

  <distributionManagement>
    <repository>
      <id>maven-core-it</id>
      <url>file:///${basedir}/repo</url>

          <description>
            A set of dependencies which the plugin requires in order to function. This enables the plugin to function
            independently of its POM (or at least to declare the libraries it needs to run).
          </description>
        </field>
      </fields>
      <codeSegments>
        <codeSegment>
          <version>2.0.0+</version>
          <code><![CDATA[

  </distributionManagement>

  <properties>
    <maven.site.path>ref/4-LATEST/${project.artifactId}</maven.site.path>
  </properties>

  <dependencyManagement>
    <!-- Not included:
         - apache-maven, as it delivers the binaries
         - maven-compat, only used by apache-maven distributions to support older releases
         - maven-slf4j-provider, only used by apache-maven distributions

specific language governing permissions and limitations
under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its.it0063</groupId>
  <artifactId>maven-it-it0063</artifactId>
  <version>1.0</version>
  <packaging>jar</packaging>

  <name>Maven Integration Test :: it0063</name>
  <description>Test the use of a system scoped dependency to a (fake) tools.jar.</description>

          <name>groupId</name>
          <version>3.0.0+</version>
          <required>true</required>
          <description>
            A universally unique identifier for a project. It is normal to
            use a fully-qualified package name to distinguish it from other
            projects with a similar name (eg. {@code org.apache.maven}).
          </description>
          <type>String</type>
        </field>
        <field>

    <classWorldsVersion>1.3</classWorldsVersion>
    <commonsCliVersion>1.0</commonsCliVersion>
    <!--

    Do not update this, Doxia will be decoupled completely from 3.x and someone can
    create a rendering engine for it if they like when the release stabilizes. JVZ

    -->
    <doxiaVersion>1.0-alpha-9</doxiaVersion>
    <easyMockVersion>1.2_Java1.3</easyMockVersion>
    <junitVersion>4.13.1</junitVersion>

    <!-- javax.inject (JSR-330) -->
    <exportedPackage>javax.inject.*</exportedPackage>
    <!-- javax.enterprise.inject (JSR-299): Must never be exported if needed at plugin level, plugin adds it
         there is no justification to get it at Maven level and leaking it will conflict.
    <exportedPackage>javax.enterprise.util.*</exportedPackage>
    <exportedPackage>javax.enterprise.inject.*</exportedPackage>
    -->

<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <plugins>
    <plugin>
      <name>Maven Integration Test Plugin</name>
      <prefix>it</prefix>
      <artifactId>maven-it-plugin</artifactId>
    </plugin>
  </plugins>

    <classWorldsVersion>1.3</classWorldsVersion>
    <commonsCliVersion>1.0</commonsCliVersion>
    <!--

    Do not update this, Doxia will be decoupled completely from 3.x and someone can
    create a rendering engine for it if they like when the release stabilizes. JVZ

    -->
    <doxiaVersion>1.0-alpha-9</doxiaVersion>
    <easyMockVersion>1.2_Java1.3</easyMockVersion>
    <junitVersion>4.13.1</junitVersion>

<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <groupId>org.apache.maven.its.plugins</groupId>
  <artifactId>maven-it-plugin</artifactId>
  <version>0.1</version>
  <versioning>
    <latest>0.1</latest>
    <release>0.1</release>
    <versions>
      <version>0.1</version>
    </versions>
    <lastUpdated>20091023233513</lastUpdated>
  </versioning>