Gradle Artifact Publishing Concepts: Difference between revisions
Jump to navigation
Jump to search
Line 30: | Line 30: | ||
Publishing plugin allow it to be [[Gradle_Maven_Publish_Plugin#Custom_Artifact_Publication|configured]]. | Publishing plugin allow it to be [[Gradle_Maven_Publish_Plugin#Custom_Artifact_Publication|configured]]. | ||
=Declaring an Artifact= | =Declaring an Artifact= |
Revision as of 15:52, 22 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 and Maven Publish, define publishing tasks, which then can be configured in build scripts and used to publish artifacts.
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. In most cases, these files are pushed to a repository.
Extension
Publishing plugin allow it to be configured.
Classifier
Publishing plugin allow it to be configured.
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