// --------------------------/
    // - Class/Member Variables -/
    // --------------------------/

    /**
     *
     *
     *             The identifier of the POM in the format {@code
     * <groupId>:<artifactId>:<version>}.
     *
     *
     */
    private String modelId;

    /**
     *
     *
     *             The path/URL of the POM or {@code null} if
     * unknown.
     *
     *

     */
    String getBuilderId();

    /**
     *
     * @param toolchains all toolchains grouped by type
     * @return this request
     * @since 3.3.0
     */
    MavenExecutionRequest setToolchains(Map<String, List<ToolchainModel>> toolchains);

    /**
     *
     * @return all toolchains grouped by type, never {@code null}
     * @since 3.3.0
     */

    <artifactId>p0</artifactId>
    <groupId>maven-t09</groupId>
    <version>1.0</version>
  </parent>
  <modelVersion>4.0.0</modelVersion>
  <groupId>maven-t09</groupId>
  <artifactId>p1</artifactId>
  <packaging>pom</packaging>
  <name>p1</name>
  <version>1.0</version>
  <scm>
    <url>scm-url</url>
  </scm>

  <dependencies>

    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>t09-a</artifactId>

 Depending on what the directory represents ("groupId", "groupId/artifactId" or "groupId/artifactId/version"),
 the Maven Repository Metadata file contains 3 different sets of metadata:

 [[1]] in a "groupId" directory: a "groupId" directory may contain Maven plugins artifacts, which are described in metadata's <<<plugins>>> element,

 [[2]] in a "groupId/artifactId" directory: metadata describes <<<groupId>>>, <<<artifactId>>> and <<<versioning>>> element that

      <unsubscribe>******@****.***</unsubscribe>
    </mailingList-->
  </mailingLists>

  <build>
    <plugins>
      <plugin>
        <groupId>inheritance.configuration</groupId>
        <artifactId>default</artifactId>
        <version>3.0</version>
        <configuration>
          <defaults>
            <parent>child</parent>
            <child>child</child>

import jcifs.smb.SID;

/**
 * Represents a group membership entry in PAC logon information.
 * Contains a group SID and associated attributes.
 */
public class PacGroup {

    private final SID id;
    private final int attributes;

    /**
     * Constructs a PAC group entry.
     * @param id the group's Security Identifier (SID)
     * @param attributes the group membership attributes
     */

  </properties>

  <dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>com.google.guava</groupId>
        <artifactId>guava</artifactId>
        <version>${project.version}</version>
      </dependency>
      <dependency>
        <groupId>com.google.guava</groupId>
        <artifactId>guava-testlib</artifactId>
        <version>${project.version}</version>
      </dependency>

unit testing.

## Adding Guava Testlib to your build

Guava testlib's Maven group ID is `com.google.guava` and its artifact ID is `guava-testlib`.

To add a dependency on Guava testlib using Maven, use the following:

```xml
<dependency>
  <groupId>com.google.guava</groupId>
  <artifactId>guava-testlib</artifactId>
  <version>33.5.0-jre</version>
  <scope>test</scope>
</dependency>
```

  </properties>
  <dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>org.jspecify</groupId>
        <artifactId>jspecify</artifactId>
        <version>${jspecify.version}</version>
      </dependency>
      <dependency>
        <groupId>com.google.errorprone</groupId>
        <artifactId>error_prone_annotations</artifactId>
        <version>${error_prone_annotations.version}</version>

  <artifactId>aid</artifactId>
  <groupId>gid</groupId>
  <version>0.1</version>

  <dependencies>
    <dependency>
      <groupId>test</groupId>
      <artifactId>a</artifactId>
      <version>0.2</version>
      <scope>system</scope>
      <systemPath>${basedir}/lib/a.jar</systemPath>
    </dependency>
    <dependency>
      <groupId>test</groupId>
      <artifactId>b</artifactId>