}

testing {
    suites {
        // tag::version-catalogs-deps[]
        val test by getting(JvmTestSuite::class) {
            dependencies {
                runtimeOnly(libs.guava)
                implementation(libs.commons.lang3)
                implementation.bundle(libs.bundles.groovy)
            }
        }
        // end::version-catalogs-deps[]
    }

class PrecompiledScriptPluginVersionCatalogIntegrationTest : AbstractKotlinIntegrationTest() {

    @Test
    fun `version catalogs main extension is available`() {
        withKotlinBuildSrc()
        withSimpleVersionCatalog()
        val scriptBody = """
            // Can use outer build version catalog when applied
            println(versionCatalogs.named("libs").findLibrary("groovy").get().get())
        """

repositories {
    mavenCentral()
}

testing {
    suites {
        // tag::version-catalogs-deps[]
        test {
            dependencies {
                runtimeOnly libs.guava
                implementation libs.commons.lang3
                implementation.bundle(libs.bundles.groovy)
            }
        }
        // end::version-catalogs-deps[]
    }

    /**
     * Configures the version catalogs which will be used to generate type safe accessors for dependencies.
     * @param spec the spec to configure the dependencies
     *
     * @since 7.0
     */
    void versionCatalogs(Action<? super MutableVersionCatalogContainer> spec);

    /**
     * Returns the configurable version catalogs.
     *
     * @since 7.0
     */

        Instrumented.fileObserved(dependenciesFile, getClass().getName());
        if (dependenciesFile.exists()) {
            dm.versionCatalogs(catalogs -> {
                VersionCatalogBuilder builder = catalogs.findByName(defaultLibrary);
                if (builder == null) {
                    builder = catalogs.create(defaultLibrary);
                }
                builder.from(services.get(FileCollectionFactory.class).fixed(dependenciesFile));

Typically, this happens if you tried to import a catalog using `from(files("some-catalog.txt"))`.

Currently Gradle only supports TOML version catalogs.

To fix this problem, either import a TOML file, or use the `Settings` API to declare your catalog.

[[catalog_file_does_not_exist]]
== Catalog file doesn't exist

This error indicates that you tried to import a catalog file, but the file doesn't exist.

 */
package org.gradle.api.initialization.resolve;

import org.gradle.api.NamedDomainObjectContainer;
import org.gradle.api.initialization.dsl.VersionCatalogBuilder;

/**
 * The container for declaring version catalogs
 *
 * @since 7.0
 */
public interface MutableVersionCatalogContainer extends NamedDomainObjectContainer<VersionCatalogBuilder> {

import java.util.Set;

/**
 * Gives access to all version catalogs available.
 *
 * @since 7.0
 */
public interface VersionCatalogsExtension extends Iterable<VersionCatalog> {

    /**
     * Tries to find a catalog with the corresponding name
     * @param name the name of the catalog
     */
    Optional<VersionCatalog> find(String name);

    /**
     * Returns the catalog with the supplied name or throws an exception

import org.gradle.util.internal.GFileUtils;

import java.io.FileWriter;
import java.io.IOException;
import java.io.PrintWriter;
import java.nio.file.Path;
import java.util.Collection;

/**
 * Generates version catalogs based on versions, libraries and plugins tracked in the BuildContentGenerationContext's VersionCatalogDependencyRegistry.
 */
@NonNullApi
public class VersionCatalogGenerator {
    final Directory target;

== Version Catalog

Version catalogs provide a way to centralize your dependency declarations in a `libs.versions.toml` file.

The catalog makes sharing dependencies and version configurations between subprojects simple.
It also allows teams to enforce versions of libraries and plugins in large projects.

The version catalog typically contains four sections: