library('my-lib', 'com.mycompany:mylib:1.2')
    }
}
// end::catalog_spec[]

// tag::catalog_publish[]
publishing {
    publications {
        maven(MavenPublication) {
            from components.versionCatalog
        }
    }
}
// end::catalog_publish[]

publishing {
    repositories {
        maven {
            url "${buildDir}/repo"
        }
    }

        library('myGroovy', 'org.codehaus.groovy:groovy:3.0.5')
    }
}

group = "com.mycompany"
version = "1.0"

publishing {
    publications {
        maven(MavenPublication) {
            from components.versionCatalog
        }
    }
}

publishing {
    repositories {
        maven {
            url "${projectDir}/repo"
        }
    }

# listed in `staging/publishing/import-restrictions.yaml`.
# Usage: `hack/verify-imports.sh`.

set -o errexit
set -o nounset
set -o pipefail

KUBE_ROOT=$(dirname "${BASH_SOURCE[0]}")/..
source "${KUBE_ROOT}/hack/lib/init.sh"

kube::golang::setup_env

GOPROXY=off go install ./cmd/importverifier

        </listitem>
        <listitem>
            <para>
                The <filename>publishing</filename> directory contains a complete example of the modern publishing plugins working with the java-gradle-plugin
                to produce two plugins shipped in the same jar and being published to both an ivy and maven repository.
            </para>

    def publishedModule = mavenRepo.module("org.gradle.test", "publishTest", "1.9")

    def "cannot publish custom component with no usages or variants"() {
        createBuildScripts("""
            publishing {
                publications {
                    maven(MavenPublication) {
                        from new MySoftwareComponent()
                    }
                }
            }
""")

        when:

Gradle is a build tool with a focus on build automation and support for multi-language development. If you are building, testing, publishing, and deploying software on any platform, Gradle offers a flexible model that can support the entire development lifecycle from compiling and packaging code to publishing web sites. Gradle has been designed to support build automation across multiple languages and platforms including Java, Scala, Android, C/C++, and Groovy, and is closely integrated with development...

        library("my-lib", "com.mycompany:mylib:1.2")
    }
}
// end::catalog_spec[]

// tag::catalog_publish[]
publishing {
    publications {
        create<MavenPublication>("maven") {
            from(components["versionCatalog"])
        }
    }
}
// end::catalog_publish[]

publishing {
    repositories {
        maven {
            url = uri("${buildDir}/repo")
        }
    }

BUILD SUCCESSFUL in 0s
${tasksExecuted.raw} actionable tasks: ${tasksExecuted.raw} executed

Publishing a build scan to scans.gradle.com requires accepting the Gradle Terms of Service defined at https://gradle.com/terms-of-service.
Do you accept these terms? [yes, no] yes

Gradle Terms of Service accepted.

Publishing build scan...
https://gradle.com/s/5u4w3gxeurtd2
----

    }

    def "can generate pom file without publishing"() {
        given:
        settingsFile << "rootProject.name = 'generatePom'"
        buildFile << """
            apply plugin: 'maven-publish'

            group = 'org.gradle.test'
            version = '1.0'

            publishing {
                repositories {
                    maven { url "${mavenRepo.uri}" }

                    api(project(":core")) { because "platform alignment" }
                    api(project(":lib")) { because "platform alignment" }
                }
            }

            publishing {
                publications {
                    maven(MavenPublication) {
                        from components.javaPlatform
                    }
                }
            }
        """