Gradle Artifact Publishing Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 21: | Line 21: | ||
=Configuration= | =Configuration= | ||
The [[Gradle_Concepts#Dependency_Configuration|configurations used to specify dependencies]] are also used to specify publishing artifacts. The "archives" configuration is the standard configuration to assign artifacts to. The [[Gradle_Java_Plugin#Overview|Java plugin]] automatically assigns the default jar to this configuration | The [[Gradle_Concepts#Dependency_Configuration|configurations used to specify dependencies]] are also used to specify publishing artifacts. | ||
The "archives" configuration is the standard configuration to assign artifacts to. The [[Gradle_Java_Plugin#Overview|Java plugin]] automatically assigns the default jar to this configuration. | |||
Revision as of 18:47, 15 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.
Configuration
The configurations used to specify dependencies are also used to specify publishing artifacts.
The "archives" configuration is the standard configuration to assign artifacts to. The Java plugin automatically assigns the default jar to this configuration.