import org.apache.maven.model.building.ModelProblemCollector;

/**
 * Handles conversion of the <code>&lt;reporting&gt;</code> section into the configuration of Maven Site Plugin 3.x,
 * i.e. <code>reportPlugins</code> and <code>outputDirectory</code> parameters.
 *
 * @deprecated since maven 4.0, this interface is not used anymore and is only here for compatibility
 */
@Deprecated
public interface ReportingConverter {

    /**

import org.gradle.api.file.FileSystemOperations
import org.gradle.api.file.RelativePath
import org.gradle.api.internal.file.FileOperations
import org.gradle.api.tasks.InputFiles
import org.gradle.api.tasks.OutputDirectory
import org.gradle.api.tasks.PathSensitive
import org.gradle.api.tasks.PathSensitivity
import org.gradle.api.tasks.TaskAction
import org.gradle.process.ExecOperations
import org.gradle.work.DisableCachingByDefault

          </execution>
        </executions>
      </plugin>
      <plugin>
        <artifactId>maven-jar-plugin</artifactId>
        <configuration>
          <archive>
            <manifestFile>${project.build.outputDirectory}/META-INF/MANIFEST.MF</manifestFile>
            <manifestEntries>
              <Multi-Release>true</Multi-Release>
            </manifestEntries>
          </archive>
          <excludes>

import org.gradle.api.logging.LogLevel
import org.gradle.api.tasks.CacheableTask
import org.gradle.api.tasks.Input
import org.gradle.api.tasks.InputFiles
import org.gradle.api.tasks.Internal
import org.gradle.api.tasks.OutputDirectory
import org.gradle.api.tasks.PathSensitive
import org.gradle.api.tasks.PathSensitivity
import org.gradle.api.tasks.TaskAction
import org.gradle.util.internal.TextUtil
import java.io.File

     * where resource {@code targetPath} elements were always interpreted as relative to the output directory
     * ({@code project.build.outputDirectory} or {@code project.build.testOutputDirectory}),
     * not the project base directory. Maven 3 plugins (like maven-resources-plugin) expect to receive
     * the relative path and perform the resolution themselves.
     * </p>

     * </p>
     * <p>
     * This behavior maintains the Maven 3.x semantic where resource {@code targetPath} elements
     * are resolved relative to the appropriate output directory ({@code project.build.outputDirectory}
     * or {@code project.build.testOutputDirectory}), <strong>not</strong> the project base directory.
     * </p>
     * <p>
     * In Maven 3, when a resource configuration specifies:
     * </p>

                val = interpolate(org);
                if (org != val) {
                    build.setTestSourceDirectory(val);
                }
                // OutputDirectory
                org = build.getOutputDirectory();
                val = interpolate(org);
                if (org != val) {
                    build.setOutputDirectory(val);
                }

                        "resources-project-builder",
                        "reporting-interpolation",
                        "target",
                        "site")),
                pom.getValue("reporting/outputDirectory"));
    }

    @Test
    void testPluginOrder() throws Exception {
        PomTestWrapper pom = buildPom("plugin-order");

        if (src != null) {
            if (sourceDominant || target.getOutputDirectory() == null) {
                target.setOutputDirectory(src);
                target.setLocation("outputDirectory", source.getLocation("outputDirectory"));
            }
        }
    }

    protected void mergeReporting_ExcludeDefaults(
            Reporting target, Reporting source, boolean sourceDominant, Map<Object, Object> context) {

            <artifactId>maven-jar-plugin</artifactId>
            <version>2.1</version>
            <configuration>
              <archive>
                <manifestFile>${project.build.outputDirectory}/META-INF/MANIFEST.MF</manifestFile>
              </archive>
            </configuration>
          </plugin>
        </plugins>
      </build>
    </profile>
    <profile>
      <id>release</id>