Gradle Artifact Publishing Concepts: Difference between revisions
Line 25: | Line 25: | ||
==Classifier== | ==Classifier== | ||
{{Internal| | {{Internal|Maven_Concepts#Classifier|Maven 'classifier'}} | ||
=<span id='Configuration'></span>Dependency Configuration= | =<span id='Configuration'></span>Dependency Configuration= |
Revision as of 01:43, 21 May 2018
External
- https://docs.gradle.org/current/userguide/artifact_management.html
- https://docs.gradle.org/current/userguide/publishing_maven.html
- https://docs.gradle.org/current/userguide/maven_plugin.html#uploading_to_maven_repositories
Internal
Overview
Publishing plugins, such as Maven, define publishing tasks, that can be configured in build.gradle.
Artifact
Projects use Gradle to produce artifacts, also referred to as publication artifacts. Artifacts of a project are the files the project provides to the outside world.
Extension
Classifier
Dependency Configuration
The configurations used to specify dependencies are also used to specify publishing artifacts. There are two configurations introduced by the Java plugin that are relevant to artifact generation and publishing: archives and runtime. Their relationship with artifact publishing is explained in the Java plugin page. Any custom archive created as part of the build are not automatically assigned to any configuration. If such as assignment is desired, it will have to be explicitly declared.
Declaring an Artifact
Publishing an Artifact
Publishing to a Maven Repository
- Gradle 1.3 and newer: Publishing to a Maven Repository with maven-publish Plugin
- Pre-Gradle 1.3 Way: Publishing to a Maven Repository with Maven Plugin