*
     * @throws TransportProviderException if passed in remote repository has invalid remote URL or unsupported protocol.
     */
    @Nonnull
    Transport transport(@Nonnull Session session, @Nonnull RemoteRepository repository);

    <artifactId>maven-api</artifactId>
    <version>4.1.0-SNAPSHOT</version>
  </parent>

  <artifactId>maven-api-metadata</artifactId>

  <name>Maven 4 API :: Repository Metadata</name>
  <description>Maven 4 API - Immutable Repository Metadata model.</description>

  <dependencies>
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-api-annotations</artifactId>
    </dependency>

 * under the License.
 */
package org.apache.maven.repository.legacy.resolver.conflict;

import javax.inject.Inject;
import javax.inject.Named;
import javax.inject.Singleton;

import org.codehaus.plexus.PlexusConstants;
import org.codehaus.plexus.PlexusContainer;
import org.codehaus.plexus.component.repository.exception.ComponentLookupException;
import org.codehaus.plexus.context.Context;

 maven 1.x and 2.x is that all project parameterization occurs in the POM and not from properties
 files.

 For many of the more advanced features in Maven2 it is critical that POMs be available in the local repository.
 Features like transitive dependencies and the new parent specification mechanism. The problem we run into is
 that currently we have information about a project scattered across the project.xml and the

        builder.pluginRepositories(null);
        return builder;
    }

    private static List<Repository> pruneRepositories(List<Repository> repositories) {
        return repositories.stream()
                .filter(r -> !org.apache.maven.api.Repository.CENTRAL_ID.equals(r.getId()))
                .collect(Collectors.toList());
    }

  <description>
    A test plugin to assist testing of Maven core.
  </description>
  <inceptionYear>2009</inceptionYear>

  <distributionManagement>
    <repository>
      <id>maven-core-it</id>
      <url>file:///${basedir}/repo</url>
    </repository>
  </distributionManagement>

  <properties>
    <maven.test.skip>true</maven.test.skip>
    <updateReleaseInfo>true</updateReleaseInfo>
  </properties>

  <description>
    A test plugin to assist testing of Maven core.
  </description>
  <inceptionYear>2009</inceptionYear>

  <distributionManagement>
    <repository>
      <id>maven-core-it</id>
      <url>file:///${basedir}/repo</url>
    </repository>
  </distributionManagement>

  <properties>
    <maven.test.skip>true</maven.test.skip>
    <updateReleaseInfo>true</updateReleaseInfo>
  </properties>

  workflow_dispatch:

permissions:
  contents: read
  id-token: write

jobs:
  cleanup-stale-performance-data:
    runs-on: ubuntu-latest

    if: github.repository == 'gradle/gradle'

    steps:
      - name: Checkout repository
        uses: actions/checkout@v6
      
      - name: Configure AWS credentials
        uses: aws-actions/configure-aws-credentials@v6
        with:

//
//   - <StorageConcurrentTasksLimit>
//     Setting reduces the parallel Repository Task slots that offload or write data to object storage. The same user interface
//     setting overwrites the storage-defined setting.
//     Optional value, default 0, range: 0-unlimited (0 equals unlimited, which means the maximum configured repository task
//     slots are used for object offloading or writing)
//
//   - <KbBlockSize>

	<property name="site.dir" value="${basedir}/src/main/webapp/WEB-INF/site" />
	<property name="kopf.branch" value="main" />

	<!-- Maven Repository -->
	<property name="maven.snapshot.repo.url" value="https://central.sonatype.com/repository/maven-snapshots" />
	<property name="maven.release.repo.url" value="https://repo1.maven.org/maven2" />

	<target name="install.jars">
		<mkdir dir="${target.dir}" />