lindsayismith
commented
1 year ago Hi Erik, great questions. I've been looking at this, and I have an initial solution, but always open to feedback.
First - setting up Maven to mirror everything through AR. Here's a settings file that will do this, but uses basic auth with a short-lived token to authenticate to AR:
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 https://maven.apache.org/xsd/settings-1.0.0.xsd">
<!-- This will ensure that all requests go through ar - but requires that we have an updated token in the auth section.
That token only lasts an hour.
To update token:
export ARTIFACT_REGISTRY_TOKEN=$(gcloud auth print-access-token)
-->
<mirrors>
<mirror>
<id>central-mirror</id>
<name>AR Maven Central mirror</name>
<url>https://us-west1-maven.pkg.dev/my-project-name/my-repository-name</url>
<mirrorOf>*</mirrorOf>
</mirror>
</mirrors>
<servers>
<server>
<id>central-mirror</id>
<username>oauth2accesstoken</username>
<password>${env.ARTIFACT_REGISTRY_TOKEN}</password>
</server>
</servers>
</settings>This makes use of the fact that Artifact Registry can take a simple username/password, where the username is 'oauth2accesstoken' and the password is a short-lived token. You have to run something like this before the build, to populate the environment variable with your token:
export ARTIFACT_REGISTRY_TOKEN=$(gcloud auth print-access-token)Running your build with these settings will pull all dependencies through the mirror you defined. The downside is that the token will expire after an hour.
You can also use this setup to bootstrap your repository with the wagon, which will help this. You can manually install the wagon like this:
mvn dependency:get -Dartifact=com.google.cloud.artifactregistry:artifactregistry-maven-wagon:2.2.1This will pull the wagon, and all it's dependencies, via the mirror you configured in the settings file, into the local repository. Make sure you use version 2.2.1, it has slimmed down dependencies compared to the prior versions.
Then, you can configure your mirror to use the wagon with two steps:
- Settings file:
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 https://maven.apache.org/xsd/settings-1.0.0.xsd">
<mirrors>
<mirror>
<id>central-mirror</id>
<name>AR Maven Central mirror</name>
<url>artifactregistry://us-west1-maven.pkg.dev/my-project-name/my-repo-name</url>
<mirrorOf>*</mirrorOf>
</mirror>
</mirrors>
</settings>- Add an extensions file to load the wagon.
This file needs to go in your project folder, in <Project Pom Root>/.mvn/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>com.google.cloud.artifactregistry</groupId>
<artifactId>artifactregistry-maven-wagon</artifactId>
<version>2.2.1</version>
</extension>
</extensions>Now, when you build your project, it will load the wagon from the local repo, and then the build will be able to talk to AR using the wagon. The wagon will provide authentication to AR from the environment, instead of using a short lived token.
recena
yanis-incepto
I'd like to take advantage of the recently released Remote and Virtual repositories features of Artifact Registry in order to make my builds resilient against intermittent connectivity to or throttling by Maven Central.
Currently, even if I forcibly populate my
~/.m2/repositorywith the full dependency tree of the plugin, if I then put in a~/.m2/settings.xmlspecifyingartifactregistry://...as a<mirrorOf>*</mirrorOf>, I get the error below:Can you please provide documentation of how to achieve the following?:
<mirrorOf>*</mirrorOf>