for the change (usually before you start working on it).  Trivial changes like typos do not
       require a JIRA issue. Your pull request should address just this issue, without
       pulling in other changes.
 - [ ] Each commit in the pull request should have a meaningful subject line and body.
 - [ ] Format the pull request title like `[MNG-XXX] SUMMARY`,

     */
    public static Properties copyProperties(Properties properties) {
        final Properties copyProperties = new Properties();
        // guard against modification/removal of keys in the given properties (MNG-5670, MNG-6053, MNG-6105)
        synchronized (properties) {
            copyProperties.putAll(properties);
        }
        return copyProperties;
    }

    }

    /* MNG-2174 */
    @Test
    void testProfilePluginMngDependencies() throws Exception {
        PomTestWrapper pom = buildPom("profile-plugin-mng-dependencies/sub", "maven-core-it");
        assertEquals("a", pom.getValue("build/plugins[1]/dependencies[1]/artifactId"));
    }

    /** MNG-4116 */
    @Test

        checkVersionsOrder(b, a); // classical
        checkVersionsOrder(b, c); // now b < c, but before MNG-5568, we had b > c
        checkVersionsOrder(a, c);
    }

    /**
     * Test <a href="https://jira.apache.org/jira/browse/MNG-6572">MNG-6572</a> optimization.
     */
    @Test
    void testMng6572() {
        String a = "20190126.230843"; // resembles a SNAPSHOT

    <version>1.0-SNAPSHOT</version>
  </parent>

  <groupId>org.apache.maven.its.mng2174</groupId>
  <artifactId>child</artifactId>
  <version>1.0-SNAPSHOT</version>

  <name>Maven Integration Test :: MNG-2174</name>
  <description>
    Verify that plugin dependencies defined by plugin management of a parent profile are not lost when the
    parent's main plugin management section is also present.
  </description>

  <build>

 * indicate at what lifecycle point it is being called.
 *
 * @see <a href="https://maven.apache.org/examples/maven-3-lifecycle-extensions.html">example</a>
 * @see <a href="https://issues.apache.org/jira/browse/MNG-4224">MNG-4224</a>
 * @since 3.0-alpha-3
 */
public abstract class AbstractMavenLifecycleParticipant {

    /**
     * Invoked after all MavenProject instances have been created.
     *

    private static final List<String> TRANSLATED_PATH_EXPRESSIONS;

    static {
        List<String> translatedPrefixes = new ArrayList<>();

        // MNG-1927, MNG-2124, MNG-3355:
        // If the build section is present and the project directory is non-null, we should make
        // sure interpolation of the directories below uses translated paths.

<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its.mng5003</groupId>
  <artifactId>mng-5003-plugin-realm-cache</artifactId>
  <version>1.0</version>

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

/**
 * Verifies scope of root project is preserved regardless of parent dependency management.
 *
 * @see <a href="https://issues.apache.org/jira/browse/MNG-2919">MNG-2919</a>
 */
@Deprecated
class ProjectInheritanceTest extends AbstractProjectInheritanceTestCase {
    // ----------------------------------------------------------------------
    //
    // p1 inherits from p0

 limitations under the License.
-->
Apache Maven
============

[![ASF Jira](https://img.shields.io/endpoint?url=https%3A%2F%2Fmaven.apache.org%2Fbadges%2Fasf_jira-MNG.json)][jira]
[![Apache License, Version 2.0, January 2004](https://img.shields.io/github/license/apache/maven.svg?label=License)][license]