<organization>
    <name>child-org</name>
  </organization>

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

    <connection>https://project.url/scm</connection>
    <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>

import org.apache.maven.project.MavenProject;

/**
 * A build context that matches a Maven project to a given task segment, and the session to be used.
 * <p>
 * A note to the reader;
 * </p>
 * <p>
 * There are several issues/discussions regarding how "aggregator" plugins should be handled.
 * Read for instance http://docs.codehaus.org/display/MAVEN/Deterministic+Lifecycle+Planning
 * </p>
 * <p>

import org.junit.jupiter.api.Test;

import static org.junit.jupiter.api.Assertions.assertEquals;

/**
 */
class DefaultExceptionHandlerTest {
    /**
     * Running Maven under JDK7 may cause connection issues because IPv6 is used by default.
     * <p>
     * e.g running mvn site:run will cause Jetty to fail.
     * </p>
     * <p>
     * The resolution is to add -Djava.net.preferIPv4Stack=true to the command line as documented in

                    Dependency present = dependencies.putIfAbsent(key, dependency);
                    if (present != null && !equals(dependency, present) && !directDependencies.contains(key)) {
                        // TODO: https://issues.apache.org/jira/browse/MNG-8004
                        problems.add(
                                Severity.WARNING,
                                Version.V40,

the concept of a project object model (POM), Maven can manage a project's
build, reporting and documentation from a central piece of information.

If you think you have found a bug, please file an issue in the [Maven Issue Tracker][jira].

Documentation
-------------

More information can be found on [Apache Maven Homepage][maven-home].
Questions related to the usage of Maven should be posted on

    <url>https://parent.url/trunk</url>
    <connection>http://parent.url/scm</connection>
    <developerConnection>https://parent.url/scm</developerConnection>
  </scm>
  <issueManagement>
    <url>https://parent.url/issues</url>
  </issueManagement>
  <ciManagement>
    <url>https://parent.url/ci</url>
  </ciManagement>
  <distributionManagement>
    <repository>
      <url>https://parent.url/dist</url>
      <id>parent.distros</id>

  <description>Commons Logging is a thin adapter allowing configurable bridging to other,
    well known logging systems.</description>
  <url>http://jakarta.apache.org/commons/logging/</url>
  <issueManagement>
    <url>http://issues.apache.org/bugzilla/</url>
  </issueManagement>
  <ciManagement>
    <notifiers>
      <notifier>
        <configuration>
          <address>******@****.***</address>
        </configuration>

    </mailingList>
    <mailingList>
      <name>Maven Issues List</name>
      <post>issues@maven.apache.org</post>
      <subscribe>issues******@****.***</subscribe>
      <unsubscribe>issues******@****.***</unsubscribe>
      <archive>http://mail-archives.apache.org/mod_mbox/maven-issues/</archive>
    </mailingList>
    <mailingList>
      <name>Maven Notifications List</name>

    - hacktoberfest
  enabled_merge_buttons:
    squash: true
    merge: false
    rebase: true
  autolink_jira:
    - MNG
notifications:
  commits: ******@****.***
  issues: issues@maven.apache.org
  pullrequests: issues@maven.apache.org