<groupId>org.apache.maven.its.mng3586</groupId>
  <artifactId>test2</artifactId>
  <version>1.0</version>

  <name>Maven Integration Test :: MNG-3586</name>
  <description>
    Test that plugin dependencies with scope system are part of the plugin class realm.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin</artifactId>

  <scm>
    <developerConnection>https://child.url/scm</developerConnection>
  </scm>
  <issueManagement>
    <url>https://child.url/issues</url>
  </issueManagement>
  <ciManagement>
    <system>child-ci</system>
    <url>https://child.url/ci</url>
  </ciManagement>
  <distributionManagement>
    <repository>
      <id>child-distros</id>
      <url>ssh://child.url/distros</url>
    </repository>

    <url>https://svn.apache.org/viewvc/spacy%20path</url>
  </scm>
  <issueManagement>
    <system>none</system>
    <url>https://issues.apache.org/spacy%20path</url>
  </issueManagement>
  <ciManagement>
    <system>none</system>
    <url>https://ci.apache.org/spacy%20path</url>
  </ciManagement>
  <distributionManagement>
    <repository>
      <id>dist</id>

    <url>https://github.com/apache/maven/tree/${project.scm.tag}/${project.artifactId}</url>
  </scm>
  <issueManagement>
    <system>jira</system>
    <url>https://issues.apache.org/jira/browse/MNG</url>
  </issueManagement>
  <ciManagement>
    <system>Jenkins</system>
    <url>https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/</url>
  </ciManagement>
  <distributionManagement>
    <site>

    <developerConnection>https://project.url/scm</developerConnection>
    <tag>TAG</tag>
  </scm>
  <issueManagement>
    <system>issues</system>
    <url>https://project.url/issues</url>
  </issueManagement>
  <ciManagement>
    <system>ci</system>
    <url>https://project.url/ci</url>
    <notifiers>
      <notifier>
        <type>irc</type>
        <address>ci@</address>

  <packaging>pom</packaging>
  <version>1.0</version>

  <dependencies>
    <dependency>
      <groupId>blah</groupId>
      <artifactId>blah</artifactId>
      <version>0.0.1-SNASPSHOT</version>
      <scope>system</scope>
      <systemPath>${basedir}/blah.jar</systemPath>
    </dependency>
  </dependencies>

    <developerConnection>https://project.url/scm</developerConnection>
    <tag>TAG</tag>
  </scm>
  <issueManagement>
    <system>issues</system>
    <url>https://project.url/issues</url>
  </issueManagement>
  <ciManagement>
    <system>ci</system>
    <url>https://project.url/ci</url>
    <notifiers>
      <notifier>
        <type>irc</type>
        <address>ci@</address>

    version number is enough for some build systems (notably, Gradle) to select
    that empty artifact over the "real" listenablefuture-1.0 -- avoiding a
    conflict with the copy of ListenableFuture in guava itself. If users are
    using an older version of Guava or a build system other than Gradle, they
    may see class conflicts. If so, they can solve them by manually excluding

		<postConstruct name="addDesignJspFileName">
			<arg>"errorNotFound"</arg>
			<arg>"error/notFound.jsp"</arg>
		</postConstruct>
		<postConstruct name="addDesignJspFileName">
			<arg>"errorSystem"</arg>
			<arg>"error/system.jsp"</arg>
		</postConstruct>
		<postConstruct name="addDesignJspFileName">
			<arg>"errorRedirect"</arg>
			<arg>"error/redirect.jsp"</arg>
		</postConstruct>
		<postConstruct name="addDesignJspFileName">

    <developerConnection>https://parent.url/scm</developerConnection>
    <tag>parent-tag</tag>
  </scm>
  <issueManagement>
    <system>parent-issues</system>
    <url>https://parent.url/issues</url>
  </issueManagement>
  <ciManagement>
    <system>parent-ci</system>
    <url>https://parent.url/ci</url>
    <notifiers>
      <notifier>
        <type>irc</type>
        <sendOnError>true</sendOnError>