import org.apache.maven.api.VersionConstraint;
import org.apache.maven.api.VersionRange;
import org.apache.maven.api.annotations.Nonnull;
import org.apache.maven.api.services.VersionParserException;

/**
 * Model builder specific version parser. It is intentionally not
 * {@link org.apache.maven.api.services.VersionParser} as this is not a service,
 * but at Maven runtime it MAY actually use that service.
 *
 * @since 4.0.0
 */

  <version>1.0-SNAPSHOT</version>

  <name>Maven Integration Test :: MNG-3821</name>
  <description>
    Verify that using the same id for executions/reportsets of different plugins doesn't blow up the project builder.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-a</artifactId>
        <version>1.0-SNAPSHOT</version>

class TestApiStandalone {

    @Test
    void testStandalone() {
        Session session = ApiRunner.createSession();

        ModelBuilder builder = session.getService(ModelBuilder.class);
        ModelBuilderResult result = builder.build(ModelBuilderRequest.builder()
                .session(session)
                .source(ModelSource.fromPath(Paths.get("pom.xml").toAbsolutePath()))
                .projectBuild(true)

    String getType();

    static ArtifactFactoryRequest build(
            Session session, String groupId, String artifactId, String version, String extension) {
        return ArtifactFactoryRequest.builder()
                .session(nonNull(session, "session cannot be null"))
                .groupId(groupId)
                .artifactId(artifactId)
                .version(version)
                .extension(extension)

        }

        return request;
    }

    // layer the creation of a project builder configuration with a request, but this will need to be
    // a Maven subclass because we don't want to couple maven to the project builder which we need to
    // separate.
    protected MavenSession createMavenSession(File pom) throws Exception {

    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-model-builder</artifactId>
    </dependency>
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-settings</artifactId>
    </dependency>
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-settings-builder</artifactId>
    </dependency>
    <dependency>
      <groupId>org.apache.maven</groupId>

    // together and this really shows the problem of constructing a sensible default configuration but
    // it's all encapsulated here so it appears normalized to the POM builder.

    // We are going to take the project packaging and find all plugin in the default lifecycle and create
    // fully populated Plugin objects, including executions with goals and default configuration taken

        Profile.Builder profile = Profile.newBuilder();

        profile.id(modelProfile.getId());

        org.apache.maven.api.model.Activation modelActivation = modelProfile.getActivation();

        if (modelActivation != null) {
            Activation.Builder activation = Activation.newBuilder();

    }

    @Override
    public int getTerminalWidth() {
        return -1;
    }

    @Override
    @Nonnull
    public MessageBuilder builder() {
        return new DefaultMessageBuilder();
    }

    @Override
    @Nonnull
    public MessageBuilder builder(int size) {
        return new DefaultMessageBuilder(new StringBuilder(size));
    }

 * is meant for exclusive consumption by the model builder and is opaque to the cache implementation. The cache key is
 * formed by a combination of group id, artifact id, version and tag. The first three components generally refer to the
 * identity of a model. The tag allows for further classification of the associated data on the sole discretion of the
 * model builder.
 *
 */
public interface ModelCache {