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

    <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>

              <!-- END default constructor on Plexus/JSR 330 components -->
              <!-- system property with that name no longer evaluated -->
              <exclude>org.apache.maven.project.DefaultProjectBuilder#DISABLE_GLOBAL_MODEL_CACHE_SYSTEM_PROPERTY</exclude>
              <exclude>org.apache.maven.project.DefaultModelBuildingListener</exclude>

    <woodstoxVersion>3.2.6</woodstoxVersion>
    <modelloVersion>1.0.1-SNAPSHOT</modelloVersion>
    <jxpathVersion>1.3</jxpathVersion>
  </properties>
  <issueManagement>
    <system>jira</system>
    <url>http://jira.codehaus.org/browse/MNG</url>
  </issueManagement>
  <mailingLists>
    <mailingList>
      <name>Maven Developer List</name>
      <subscribe>******@****.***</subscribe>

    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

		<packaging.fess.group>fess</packaging.fess.group>
		<packaging.fess.pid.dir>/var/run/fess</packaging.fess.pid.dir>
		<packaging.fess.systemd.dir>/usr/lib/systemd/system</packaging.fess.systemd.dir>
		<packaging.fess.systemd.sysctl.dir>/usr/lib/sysctl.d</packaging.fess.systemd.sysctl.dir>
		<packaging.fess.tmpfilesd.dir>/usr/lib/tmpfiles.d</packaging.fess.tmpfilesd.dir>

    <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>

  <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://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>