This Maven extension allows to add additional remote repositories to the Maven execution by solely using OS level environment variables or Java system properties (without touching settings.xml nor pom.xml). Furthermore it allows to place certain artifacts directly under .mvn/repository (see details below). This is achieved by modifying the in-memory Maven settings before using them.

While most of the time setting the remote repositories in the settings.xml (and potentially also in pom.xml) is the recommended approach, for cases where the settings.xml is not under the development team's control it can be useful to configure this extension.

In case the relevant environment variables are not set this extension has no effect (apart from the implicit file repo .mvn/repository if it exists). This allows to

• Minimise the changes in the regular project setup (only the extension has to be added, all mirrors, repositories from settings.xml may remain active for local developers or CI servers)
• Add additional repositories with the help of environment variables or system properties.

This is helpful for constrained build environments (without full control over the settings.xml file) and also to enforce a common repository across all developers without additional manual set up. As this extension always adds a new repository it is mostly useful for cases where no POM repositories are being used. Just adding credentials for an existing (POM or settings.xml) repository is not supported yet (issue 28).

In directory .mvn, create (or adjust) the file extensions.xml:

<extensions xmlns="http://maven.apache.org/EXTENSIONS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/EXTENSIONS/1.0.0 http://maven.apache.org/xsd/core-extensions-1.0.0.xsd">
    <extension>
        <groupId>biz.netcentric.maven.extension</groupId>
        <artifactId>maven-ext-repos-from-env</artifactId>
        <version>1.2.0</version>
    </extension>
</extensions>

See Maven documentation for reference on how extensions can be activated.

The artifact is available at Maven Central.

In all the following examples environment variables are used, but this extension can also be configured with Java system properties having the same name as the environment variables. In case both a variable and property are given with the same name the system property takes precedence.

The following environment variables can be set to have the Maven extension above automatically add both the repository (could be otherwise in pom.xml or in settings.xml) and the authentication for the server (would have to be configured in settings.xml without this extension):

export MVN_SETTINGS_REPO_URL=https://repo.myorg.com/path/to/repo
export MVN_SETTINGS_REPO_USERNAME=username
export MVN_SETTINGS_REPO_PASSWORD=password

This leads to using authentication via basic auth to the given repository.

For the case no authentication is necessary, setting only one environment variable is sufficient:

export MVN_SETTINGS_REPO_URL=https://repo.myorg.com/path/to/repo_no_auth

For this case, no corresponding server entry is generated for this repository.

It is also possible to use multiple repositories by placing an infix between the environment prefix MVN_SETTINGS_REPO and the configuration specific suffix:

# REPO_NAME1
export MVN_SETTINGS_REPO_NAME1_URL=https://repo.myorg.com/path/to/repo
export MVN_SETTINGS_REPO_NAME1_USERNAME=username1
export MVN_SETTINGS_REPO_NAME1_PASSWORD=password1
# REPO_NAME2
export MVN_SETTINGS_REPO_NAME2_URL=https://repo.myorg.com/path/to/repo
export MVN_SETTINGS_REPO_NAME2_USERNAME=username2
export MVN_SETTINGS_REPO_NAME2_PASSWORD=password2

In this example two repositories and two server entries for are created. The order can be important for performance reasons, the repositories are added in alphabetical order of their names.

As generally true for Maven repositories, it is also possible to use file urls. To reference a file repository within the build repository itself, use the property maven.multiModuleProjectDirectory in the value of MVN_SETTINGS_REPO_URL, e.g. MVN_SETTINGS_REPO_URL=file://${maven.multiModuleProjectDirectory}/vendor1/repository. If the directory .mvn/repository exists, it is automatically added as file repository.

This approach can be useful for parent poms or importing dependencies (scope import).

With the environment variable MVN_SETTINGS_REPO_LOG_VERBOSE, some more logging can be activated:

export MVN_SETTINGS_REPO_LOG_VERBOSE=true

In case the settings.xml defines one or multiple mirrors, those are automatically disabled for the newly added repositories by adding their ids to the mirrorOf value with a leading ! as documented in Advanced Mirror Specification. To disable this mirror bypass set the environment variable MVN_DISABLE_BYPASS_MIRRORS to true.

By default, the repositories as configured in env are queried after the default repositories in settings.xml. For the case that the system env repo is also a proxy repository for Maven Central (i.e. containing all required artifacts), it can be forced to be used first (before the repositories from settings.xml).

export MVN_SETTINGS_ENV_REPOS_FIRST=true

Setting this flag is only relevant for performance reasons, the overall build will work with or without this flag. For the general order of repositories (both from settings and POM) refer to https://maven.apache.org/guides/mini/guide-multiple-repositories.html#repository-order.

In case environment variables are too much effort to set one can also leverage the .mvn/jvm.config file to set the configuration via Java system properties.

An example file might look like this

-DMVN_SETTINGS_REPO_NAME1_URL=https://repo.myorg.com/path/to/repo -DMVN_SETTINGS_REPO_NAME1_USERNAME=username1 -DMVN_SETTINGS_REPO_NAME1_PASSWORD=password1

Such a configuration can be distributed through the SCM along with the code (in case the values are not supposed to be treated as secrets).

Reference the Maven extension in the .mvn/extensions.xml file as described above.

Prerequisites:

• Add the Cloud Manager API to your Adobe IO project at https://console.adobe.io/
  • Add a Service Account (JWT based) by either uploading a public key (from a manually generated private/public key pair) or letting the wizard generate both private and public key for you. In both cases make sure to store the private key in a safe place.
  • Setting environment variables requires permissions of role Deployment Manager so make sure that the service account has at least that permission
• Install aio-cli
• Setup Adobe IO CLI in general Getting Started
• Install aio-cli-plugin-cloudmanager
• Setup Adobe IO authentication with Cloud Manager

Once everything is set up, the environment variables of the Cloud Manager build can be set as follows:

aio cloudmanager:set-pipeline-variables \
   <PIPELINE_ID> \
   --programId=<PROGRAM_ID> \
   --variable \
     MVN_SETTINGS_REPO_URL <REPO_URL> \
     MVN_SETTINGS_REPO_USERNAME <REPO_USER> \
   --secret \
     MVN_SETTINGS_REPO_PASSWORD <REPO_PASSWORD>  

The parameters <PIPELINE_ID> and <PROGRAM_ID> can be derived from URLs when browsing the Cloud Manager. The call needs to be made for each pipeline as set up in cloud manager (all non-prod and the prod pipeline).

See also official Adobe documentation and reference on GitHub