Skip to content

Commit 48c4e7d

Browse files
author
Rami Bououni
committed
edit + moniker
1 parent 23b9a08 commit 48c4e7d

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

docs/pipelines/artifacts/publish-maven-artifacts.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,8 @@ monikerRange: '>= azure-devops-2020'
88

99
# Publish Maven artifacts with Azure Pipelines (YAML/Classic)
1010

11+
[!INCLUDE [version-gt-eq-2020](../../includes/version-gt-eq-2020.md)]
12+
1113
Azure Pipelines enables developers to publish Maven artifacts to Azure Artifacts feeds within the same organization, across other organizations, and to public registries such as Maven Central. This article guides you through publishing your Maven artifacts using both YAML and Classic pipelines.
1214

1315
## Prerequisites
@@ -74,7 +76,7 @@ Azure Pipelines enables developers to publish Maven artifacts to Azure Artifacts
7476
> [!NOTE]
7577
> To publish packages to a feed using Azure Pipelines, make sure that both the **Project Collection Build Service** and your project's **Build Service** identities are assigned the **Feed Publisher (Contributor)** role in your feed settings. See [Manage permissions](../../artifacts/feeds/feed-permissions.md#pipelines-permissions) for more details.
7678

77-
## Publish packages to a feed in another organization
79+
## Publish packages to a feed in a different organization
7880

7981
To publish packages to a feed in a different Azure DevOps organization, you must first create a personal access token (PAT) in the target organization.
8082

0 commit comments

Comments
 (0)