Apache Maven Distribution Tools

Clone this repo:
  1. addf123 Maven leaf logo in higher quality (#199) by Matthias Bünger · 21 hours ago master
  2. a27a00e Bump com.fasterxml.jackson:jackson-bom from 2.22.0 to 2.22.1 (#197) by dependabot[bot] · 2 days ago
  3. ac6a380 Bump org.eclipse.jetty:jetty-server from 12.1.10 to 12.1.11 (#196) by dependabot[bot] · 2 days ago
  4. 96c5053 Bump org.eclipse.jetty:jetty-client from 12.1.9 to 12.1.11 (#198) by dependabot[bot] · 2 days ago
  5. efbd436 Bump org.apache.maven:maven-parent from 48 to 49 (#195) by dependabot[bot] · 13 days ago

Apache Maven Distribution Tool

Apache License, Version 2.0, January 2004 Jenkins Status

Maven Distribution Tool is a tool executed daily on Maven CI server to produce a report of the different checks done on our releases.

Quick Build

mvn verify site

Configuration

API_TOKEN

The API_TOKEN environment variable is required to authenticate HTTP requests against the Apache Jenkins instance and other Apache infrastructure. It is a Base64-encoded username:apitoken string used for HTTP Basic Authentication.

Generating the Token

  1. Log in to the Apache Jenkins instance.
  2. Click your username in the top-right corner to open your user profile.
  3. Navigate to Security (or go directly to https://ci-maven.apache.org/user/<your-username>/security/).
  4. Under API Token, click Add new Token, give it a name, and click Generate.
  5. Copy the generated token — it will not be shown again.

Setting the Environment Variable

Base64-encode your Jenkins username and API token, then export it:

export API_TOKEN=$(echo -n 'your-username:your-api-token' | base64)

You can add this to your shell profile (~/.bashrc, ~/.zshrc, etc.) for persistence.

Usage

  • Local build with site reports: mvn verify site — the reports use API_TOKEN to fetch data from Jenkins.
  • Integration tests: mvn failsafe:integration-test — the token is passed to the failsafe plugin via the API_TOKEN environment variable.
  • CI (Jenkins): The token is automatically injected via the withCredentials binding in the Jenkinsfile using the API_TOKEN credential ID.