import org.apache.maven.model.v4.MavenMerger;
import org.junit.jupiter.api.Test;

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

/**
 * MavenMerger is based on same instances, subclasses should override KeyComputer per type
 */
class MavenMergerTest {
    private MavenMerger mavenMerger = new MavenMerger();

    @Test
    void mergeArtifactId() {

import org.apache.maven.model.v4.MavenMerger;
import org.junit.jupiter.api.Test;

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

@Deprecated
class FileToRawModelMergerTest {

    /**
     * Ensures that all list-merge methods are overridden
     */
    @Test
    void testOverriddenMergeMethods() {
        List<String> methodNames = Stream.of(MavenMerger.class.getDeclaredMethods())

import org.apache.maven.api.model.PluginContainer;
import org.apache.maven.api.model.Profile;
import org.apache.maven.api.model.ReportPlugin;
import org.apache.maven.api.model.Reporting;
import org.apache.maven.model.v4.MavenMerger;

/**
 * As long as Maven controls the BuildPomXMLFilter, the entities that need merging are known.
 * All others can simply be copied from source to target to restore the locationTracker
 *
 * @since 4.0.0