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

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

    <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>jar</packaging>

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

  <dependencies>
    <dependency>
      <groupId>com.sun</groupId>
      <artifactId>tools</artifactId>
      <version>1.4.2</version>
      <scope>system</scope>
      <systemPath>${jre.home}/../lib/tools.jar</systemPath>
    </dependency>
  </dependencies>

  <packaging>jar</packaging>

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

  <dependencies>
    <dependency>
      <groupId>com.sun</groupId>
      <artifactId>tools</artifactId>
      <version>1.4.2</version>
      <scope>system</scope>
      <systemPath>${jre.home}/../lib/tools.jar</systemPath>
    </dependency>
  </dependencies>

  </parent>

  <name>Guava BOM</name>
  <description>BOM for Guava artifacts</description>
  <url>https://github.com/google/guava</url>
  <inceptionYear>2010</inceptionYear>

  <issueManagement>
    <system>GitHub Issues</system>
    <url>https://github.com/google/guava/issues</url>
  </issueManagement>

  <licenses>
    <license>
      <name>Apache License, Version 2.0</name>

under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>gid</groupId>
  <artifactId>aid</artifactId>
  <version>1.0</version>

  <name>${system.property}</name>

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