# Gradle Module Metadata 1.0 specification

Consumption of Gradle Module Metadata is automatic. However, publication needs to be enabled explicitly for any Gradle version prior to Gradle 6.

Publishing Gradle Module Metadata can be enabled in the Gradle settings file (`settings.gradle`):

```
enableFeaturePreview("GRADLE_METADATA")
```

## Goal

This ADR does not specify the owner of this new architecture module. However, as a separate module, it can be assigned ownership independently of the other core services.

## Status

ACCEPTED

## Consequences

- Introduce the module and move the services and their implementations.

Tom Tresansky <******@****.***> 1696954098 -0400

        setup:
        file("src/main/java/module-info.java") << """
            module my.module {
                requires jmodule
                requires jautomodule
            }
        """

        when:
        succeeds "eclipse"

        then:
        def libraries = classpath.libs
        libraries.size() == 3
        libraries[0].jarName == 'jmodule-1.0.jar'

Laura Kassovic <******@****.***> 1701107622 -0800

Laura Kassovic <******@****.***> 1701107622 -0800

Paul Merlin <******@****.***> 1696084526 +0200

        └── module-info.java
```

In the module info file, you declare a _module name_, which packages of your module you want to _export_ and which other modules you _require_.

[source,java,indent=0]
.module-info.java file
----
include::{snippetsPath}/java-library/module/groovy/src/main/java/module-info.java[]
----

            //
            // We assume that a test-only dependency is not a module, which corresponds to how Eclipse does test running for modules:
            // It patches the main module with the tests and expects test dependencies to be part of the unnamed module (classpath).
            return javaModuleDetector.isModule(inferModulePath && !testOnly, artifact);
        }

        and:
        repoA = mavenRepo("maven-repo")
        repoB = ivyRepo("ivy-repo")

        and:
        def abModule = publishPlugin(pluginAB, repoB).pluginModule
        (publishPlugin(pluginA, repoA).pluginModule as MavenModule)
            .dependsOn(abModule.group, abModule.module, abModule.version)
            .publishPom()

        and:
        use(repoB, repoA)

        and:
        buildFile << """