Cloud customer?
Start for Free >
Upgrade in MyJFrog >
What's New in Cloud >


The Maven Artifactory Plugin, Artifactory is fully integrated with Maven builds and allows you to do the following:
  1. Attach properties to published artifacts in Artifactory metadata.
  2. Capture a Build Info object which can be passed to the Artifactory REST API to provide a fully traceable build context.
  3. Automatically publish all build artifacts at the end of the build.

Source Code Available!

The Maven Artifactory Plugin is an open-source project on GitHub which you can freely browse and fork.

Page Contents



The Maven Artifactory Plugin coordinates are org.jfrog.buildinfo:artifactory-maven-plugin:x.x.x. It can be viewed on

A typical build plugin configuration would be as follows:


The plugin's invocation phase is validate by default and we recommend you don't change it so the plugin is called as early as possible in the lifecycle of your Maven build.


The example above configures the Artifactory publisher,  to deploy build artifacts either to the releases or the snapshots repository of the  public OSS instance of Artifactory when mvn deploy is executed. 

However, the Maven Artifactory Plugin provides many other configurations which you can see by running mvn -X validate and are displayed below:

<deployProperties> .. </deployProperties>
  <envVarsExcludePatterns> .. </envVarsExcludePatterns>
  <envVarsIncludePatterns> .. </envVarsIncludePatterns>
  <contextUrl> .. </contextUrl>
  <username> .. </username>
  <password> .. </password>
  <repoKey> .. </repoKey>
  <snapshotRepoKey> .. </snapshotRepoKey>
  <excludePatterns> .. </excludePatterns>
  <includePatterns> .. </includePatterns>
  <!-- If true build information published to Artifactory will include implicit project as well as build-time dependencies -->
  <!-- Minimum file size in KB for which the plugin performs checksum deploy optimization. Default: 10. Set to 0 to disable uploading files with checksum that already exists in Artifactory. -->
  <agentName> .. </agentName>
  <agentVersion> .. </agentVersion>
  <buildName> .. </buildName>
  <buildNumber> .. </buildNumber>
  <!-- If you'd like to associate the published build-info with a JFrog Project, add the project key here -->
  <project> .. </project> 
  <buildNumbersNotToDelete> .. </buildNumbersNotToDelete>
  <buildUrl> .. </buildUrl>
  <principal> .. </principal>

Specifies properties you can attach to published artifacts. For example:

 Specifies whether environment variables are published as part of BuildInfo metadata and which include or exclude patterns are applied when variables are collected

Defines an Artifactory repository where build artifacts should be published using a combination of a <contextUrl> and <repoKey>/<snapshotRepoKey>.

Build artifacts are deployed if the deploy goal is executed and only after all modules are built

Updates BuildInfo metadata published together with build artifacts. You can configure whether or not BuildInfo metadata is published using the <publisher> configuration.

Reading Environment Variables and System Properties

Every build server provides its own set of environment variables. You can utilize these variables when configuring the plugin as shown in the following example:



Any plugin configuration value can contain several {{ .. }} expressions. Each expression can contain a single or multiple environment variables or system properties to be used.

The expression syntax allows you to provide enough variables to accommodate any build server requirements according to the following rules:

  • Each expression can contain several variables, separated by a  ' | ' character to be used with a configuration value
  • The last value in a list is the default that will be used if none of the previous variables is available as an environment variable or a system property

For example, for the expression {{V1|V2|"defaultValue"}} the plugin will attempt to locate environment variable V1, then system property V1, then environment variable or system property V2, and if none of these is available, "defaultValue" will be used. 

If the last value is not a string (as denoted by the quotation marks) and the variable cannot be resolved, null will be used (for example, for expression {{V1|V2}} where neither V1 nor V2 can be resolved).  


The following project provides a working example of using the plugin:

Maven Artifactory Plugin

Release Notes

3.5.3 (23 March 2023)
  • Filter settings.xml properties without collecting env vars
3.5.2 (13 March 2023)
  • Filter build-info and modules properties
3.5.1 (27 Nov 2022)
  • Pom doesn't get deployed using Maven Install plugin 3+
3.5.0 (24 Nov 2022)
  • Support maven.deploy.skip property on a module
  • Update dependencies
3.4.0 (14 Feb 2021)
  • Add support for artifactory projects.
  • Verify artifact type length limit (64).
  • Update build-info to 2.35.0.
3.3.0 (12 Sep 2021)
  1. Populate build-info with VCS information.
3.2.3 (6 Jun 2021)
  1. Update build-info-extractor to 2.26.4.
3.2.1 (16 February 2021)
  1. Plugin is uploaded to Maven Central.
  2. Bugfix - Replaced variables are overridden after a project started.
3.2.0 (18 January 2021)
  1. Allow plugin to be inherited.
  2. Allow configuring the minimal file size for the checksum deploy algorithm.
3.1.0 (14 January 2021)
  1. Reintroduce the expression syntax algorithm of environment and system variables.
3.0.0 (30 September 2020)
  1. Migrate code base from to
  2. Parallel artifacts deployment using 3 threads.
  3. Build-info - Populate the Build Agent with the plugin name and version.
  4. Breaking changes: <licenses> and <blackDuck> configurations had been removed.
  5. Breaking changes: The expression syntax algorithm of environment and system variables had been removed.
  • No labels
Copyright © 2023 JFrog Ltd.