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

 * under the License.
 */
package org.apache.maven.lifecycle.internal;

import java.util.Set;

import org.apache.maven.artifact.Artifact;
import org.apache.maven.project.MavenProject;
import org.apache.maven.project.artifact.InvalidDependencyVersionException;

/**
 * <p>
 * Component interface responsible for creation of MavenProject#dependencyArtifacts instances.
 * </p>

import java.util.Collections;
import java.util.HashSet;
import java.util.Properties;
import java.util.Set;

import org.apache.maven.AbstractCoreMavenComponentTestCase;
import org.apache.maven.artifact.Artifact;
import org.apache.maven.execution.MavenSession;
import org.apache.maven.project.MavenProject;
import org.junit.jupiter.api.Test;

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

        List<String> elements = project.getCompileClasspathElements();
        assertEquals(2, elements.size());

        @SuppressWarnings("deprecation")
        List<Artifact> artifacts = project.getCompileArtifacts();
        assertEquals(1, artifacts.size());
        assertTrue(artifacts.get(0).getFile().getName().endsWith("tools.jar"));
    }

  It is more than simply understanding that m2 cannot go and check for the
  latest version of some snapshot artifact. If m2 is offline, SCM operations
  cannot succeed; no artifact downloads can take place, regardless of whether
  they are snapshot versions; artifact deployment cannot take place; certain
  types of tests cannot be setup, since the container used to run them cannot be
  reached or started.

    <groupId>inheritance</groupId>
    <artifactId>parent</artifactId>
    <version>11-SNAPSHOT</version>
  </parent>

  <groupId>inheritance</groupId>
  <artifactId>child-artifact-id</artifactId>
  <version>11-SNAPSHOT</version>
  <name>Model urls inheritance test child</name>
  <description>Flat directory structure case: module = ../child directory path + child directory path != child-artifact-id</description>

        assertEquals("bar", project.getProperties().getProperty("foo"));

        ArrayList<Artifact> artifacts = new ArrayList<>(project.getArtifacts());

        assertEquals(1, artifacts.size());
        assertEquals(INJECTED_ARTIFACT_ID, artifacts.get(0).getArtifactId());
    }

    @Test
    void testReactorDependencyInjection() throws Exception {

    }

    @Nonnull
    @Override
    public List<ProducedArtifact> getArtifacts() {
        org.eclipse.aether.artifact.Artifact pomArtifact = RepositoryUtils.toArtifact(new ProjectArtifact(project));
        org.eclipse.aether.artifact.Artifact projectArtifact = RepositoryUtils.toArtifact(project.getArtifact());

        ArrayList<ProducedArtifact> result = new ArrayList<>(2);

 * specific language governing permissions and limitations
 * under the License.
 */
package org.apache.maven.artifact.repository.metadata;

import org.apache.maven.artifact.repository.ArtifactRepository;
import org.apache.maven.artifact.repository.ArtifactRepositoryPolicy;

/**
 * Describes repository directory metadata.
 *
 * TODO not happy about the store method - they use "this"
 */

            the filename after the version. This allows:
            <ul>
            <li>referring to attached artifact, for example {@code sources} and {@code javadoc}:
            see <a href="../maven-core/artifact-handlers.html">default artifact handlers</a> for a list,</li>
            <li>distinguishing two artifacts
            that belong to the same POM but were built differently.