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

    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

  <artifactId>test</artifactId>
  <version>1.0-SNAPSHOT</version>

  <name>Maven Integration Test :: it0021</name>
  <description>
    Test pom-level profile inclusion (this one is activated by system property).
  </description>

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

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

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