isLast()
                }
            }
        }
    }

    def "dependencies with multiple dependency artifacts are mapped to multiple dependency declarations in GMM"() {
        given:
        settingsFile << "rootProject.name = 'root'"
        buildFile << """
            plugins {
                id("java-library")
                id("maven-publish")
            }

BUILD SUCCESSFUL in 331ms
----

The `publishToMavenLocal` task builds the POM file and the artifacts to be published.
It then _installs_ them into the local Maven repository.

You can view the POM and GMM file in the `build` directory:

image::tutorial/intellij-idea-dist.png[]

You can also view the files in your Maven Local directory: `/Users/\[username]/.m2/repository/com/gradle/tutorial/tutorial/1.0`.

[source,xml]

====

With the changes above, the generated Gradle Module Metadata file will always be different, forcing downstream tasks to consider it out-of-date.

[[sub:disabling-gmm-publication]]
== Disabling Gradle Module Metadata publication

There are situations where you might want to disable publication of Gradle Module Metadata:

            }

            $append
        """
    }

    @ToBeFixedForConfigurationCache
    def "dependencies with multiple dependency artifacts are mapped to multiple dependency declarations in GMM"() {
        def repoModule = javaLibrary(ivyRepo.module('group', 'root', '1.0'))

        given:
        settingsFile << "rootProject.name = 'root'"
        buildFile << """
            apply plugin: "java-library"

        def dependency = dependencies.values().first()
        dependency.groupId == "org.jetbrains.kotlinx"
        dependency.artifactId == "kotlinx-coroutines-core-jvm"
        dependency.version == "1.7.2"

        // GMM continues to use component coordinates
        def gmmDependencies = repoModule.parsedModuleMetadata.variant("runtimeElements").dependencies
        gmmDependencies.size() == 1
        def gmmDependency = gmmDependencies.first()

            assert files*.name == []
        }
    }

    @Issue("https://github.com/gradle/gradle/issues/20581")
    void "warn deprecated behavior when GMM is modified after a Maven publication is populated"() {
        given:
        buildFile << """
            plugins {
                id("java-library")
                id("maven-publish")
            }

    }

    private expectModuleServed(MavenHttpModule module, boolean pom, boolean gmm) {
        if (module.version.endsWith('-SNAPSHOT')) {
            module.metaData.expectGet()
        }
        if (pom) {
            module.pom.expectGet()
        }
        if (gmm) {
            module.moduleMetadata.expectGet()
        }
        module.artifact.expectGet()
    }

 *
 * <p>This builder extracts the variants, dependencies, artifacts, etc from the component to build
 * an independent representation of a GMM file that can be published without additional processing.</p>
 */
public class ModuleMetadataSpecBuilder {

    private final PublicationInternal<?> publication;
    private final ModuleVersionIdentifier publicationCoordinates;

----
=====
====


[[gmm_modification_after_publication_populated]]
==== Modifying Gradle Module Metadata after a publication has been populated

Altering the link:publishing_gradle_module_metadata.html[GMM] (e.g., changing a component configuration variants) *after* a Maven or Ivy publication has been populated from their components is now deprecated.
This feature will be removed in Gradle 9.0.