Gradle Artifacts: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Internal= * Gradle Concepts * Gradle Artifact Publishing Concepts =Overview= A Gradle project may...") |
No edit summary |
||
| Line 1: | Line 1: | ||
=Internal= | =Internal= | ||
* [[Gradle Concepts#|Gradle Concepts]] | * [[Gradle Concepts#Artifacts_and_Artifact_Publishing|Gradle Concepts]] | ||
* [[ Gradle_Artifact_Publishing_Concepts#Overview|Gradle Artifact Publishing Concepts]] | * [[ Gradle_Artifact_Publishing_Concepts#Overview|Gradle Artifact Publishing Concepts]] | ||
=Overview= | =Overview= | ||
Revision as of 00:49, 24 February 2019
Internal
Overview
A Gradle project may produce zero, one or more artifacts. An artifact may be built locally by a plugin such as the Application plugin, which in turn delegates the artifact building part to Distribution plugin, or by other plugins. The artifact building plugins create the artifact locally, in the project build area. This article describes the process of configuring and executing the artifact generation. For details on how the artifacts can be published, see:
Artifact
A Gradle artifact is a file the project builds and shares with the outside world.