---
title: "Maven Repository"
description: "Add the ConfigDirector Maven repository to a Gradle or Maven build to install the Android and Java SDKs, and verify the files it serves"
canonical_url: "https://docs.configdirector.com/sdks/maven-repository"
---
# Maven Repository

> Add the ConfigDirector Maven repository to a Gradle or Maven build to install the Android and Java SDKs, and verify the files it serves

The ConfigDirector Android and Java SDKs, and the OpenFeature providers built on them, are published to the ConfigDirector Maven repository:

```txt
https://maven.configdirector.com
```

Anyone can download from it, without an account or credentials. Once a version is published there it never changes: its files are never replaced or deleted.

## Artifacts

<table>
<thead>
  <tr>
    <th>
      Artifact
    </th>
    
    <th>
      Contents
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        com.configdirector:android-sdk
      </code>
    </td>
    
    <td>
      The <a href="https://docs.configdirector.com/sdks/mobile/android">
        Android SDK
      </a>
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        com.configdirector:android-sdk-compose
      </code>
    </td>
    
    <td>
      Jetpack Compose bindings for the Android SDK
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        com.configdirector:android-sdk-testing
      </code>
    </td>
    
    <td>
      Tools for testing code that uses the Android SDK
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        com.configdirector:openfeature-android-provider
      </code>
    </td>
    
    <td>
      The <a href="https://docs.configdirector.com/sdks/openfeature/android">
        OpenFeature Android provider
      </a>
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        com.configdirector:server-sdk
      </code>
    </td>
    
    <td>
      The <a href="https://docs.configdirector.com/sdks/server/java">
        Java server SDK
      </a>
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        com.configdirector:server-sdk-testing
      </code>
    </td>
    
    <td>
      Tools for testing code that uses the Java server SDK
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        com.configdirector:openfeature-server-provider
      </code>
    </td>
    
    <td>
      The <a href="https://docs.configdirector.com/sdks/openfeature/java">
        OpenFeature Java provider
      </a>
    </td>
  </tr>
</tbody>
</table>

### Older versions on Maven Central

Versions up to Android SDK 1.6.0, OpenFeature Android provider 1.2.0, Java server SDK 1.7.0 and OpenFeature Java provider 1.4.0 were published to Maven Central under older names. Newer versions are only in this repository.

<table>
<thead>
  <tr>
    <th>
      Name on Maven Central
    </th>
    
    <th>
      Name in this repository
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        configdirector-android
      </code>
    </td>
    
    <td>
      <code>
        android-sdk
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        configdirector-android-compose
      </code>
    </td>
    
    <td>
      <code>
        android-sdk-compose
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        configdirector-android-testing
      </code>
    </td>
    
    <td>
      <code>
        android-sdk-testing
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        configdirector-openfeature-android-provider
      </code>
    </td>
    
    <td>
      <code>
        openfeature-android-provider
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        configdirector-server-sdk
      </code>
    </td>
    
    <td>
      <code>
        server-sdk
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        configdirector-server-sdk-testing
      </code>
    </td>
    
    <td>
      <code>
        server-sdk-testing
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        configdirector-openfeature-server-provider
      </code>
    </td>
    
    <td>
      <code>
        openfeature-server-provider
      </code>
    </td>
  </tr>
</tbody>
</table>

To upgrade from a version on Maven Central, add the repository to your build and change the artifact names. Change all of them at once: an artifact under its old name and the same artifact under its new name contain the same classes, so they cannot be on the same classpath.

## Add the repository to your build

### Gradle

If your build declares its repositories in `settings.gradle.kts` or `settings.gradle`, under `dependencyResolutionManagement`, add the repository there. Android Studio sets up new projects this way, and their builds fail if a module's build file declares a repository.

<code-group>

```kotlin [settings.gradle.kts]
dependencyResolutionManagement {
    repositories {
        google()
        mavenCentral()
        exclusiveContent {
            forRepository {
                maven {
                    name = "ConfigDirector"
                    url = uri("https://maven.configdirector.com")
                }
            }
            filter {
                includeGroup("com.configdirector")
            }
        }
    }
}
```

```groovy [settings.gradle]
dependencyResolutionManagement {
    repositories {
        google()
        mavenCentral()
        exclusiveContent {
            forRepository {
                maven {
                    name = 'ConfigDirector'
                    url = 'https://maven.configdirector.com'
                }
            }
            filter {
                includeGroup 'com.configdirector'
            }
        }
    }
}
```

</code-group>

Otherwise, add it to the `repositories` block of your build file:

<code-group>

```kotlin [build.gradle.kts]
repositories {
    mavenCentral()
    exclusiveContent {
        forRepository {
            maven {
                name = "ConfigDirector"
                url = uri("https://maven.configdirector.com")
            }
        }
        filter {
            includeGroup("com.configdirector")
        }
    }
}
```

```groovy [build.gradle]
repositories {
    mavenCentral()
    exclusiveContent {
        forRepository {
            maven {
                name = 'ConfigDirector'
                url = 'https://maven.configdirector.com'
            }
        }
        filter {
            includeGroup 'com.configdirector'
        }
    }
}
```

</code-group>

With `exclusiveContent`, Gradle looks for ConfigDirector artifacts only in this repository, and looks for nothing else there. Keep the other repositories your build already lists.

### Maven

Add the repository to `pom.xml`:

```xml [pom.xml]
<repositories>
  <repository>
    <id>configdirector</id>
    <url>https://maven.configdirector.com</url>
    <releases><enabled>true</enabled></releases>
    <snapshots><enabled>false</enabled></snapshots>
  </repository>
</repositories>
```

## Dependabot

On GitHub.com, `.github/dependabot.yml` needs no registry entry for this repository. Dependabot finds the repository in `pom.xml`, or in your Gradle settings file or top-level build file, and opens pull requests for new versions of the SDKs.

Add the registry entry, without credentials, if your repositories are on GitHub Enterprise Server, or if your Gradle build adds this repository only in a module's build file or in a convention plugin:

```yaml [.github/dependabot.yml]
version: 2
registries:
  configdirector:
    type: maven-repository
    url: https://maven.configdirector.com
updates:
  - package-ecosystem: "gradle"
    directory: "/"
    registries:
      - configdirector
    schedule:
      interval: "weekly"
```

For a Maven build, the `package-ecosystem` is `"maven"`. If the file already has `updates` entries, add `configdirector` to the `registries` of each entry that covers a build using the SDKs.

If `.github/dependabot.yml` already has a `configdirector` registry and neither case applies, you can remove it, along with `configdirector` in the `registries` of each `updates` entry.

## Company repository managers

If your builds download their dependencies through a repository manager such as Sonatype Nexus Repository or JFrog Artifactory, rather than from public repositories directly, its administrator adds this repository once:

1. Create a Maven proxy repository (a remote repository in Artifactory) with `https://maven.configdirector.com` as its URL. It only serves release versions and needs no credentials.
2. Limit it to the `com.configdirector` group: in Nexus with a routing rule that allows `^/com/configdirector/.*`, in Artifactory with the include pattern `com/configdirector/**`.
3. Add it to the group repository (the virtual repository in Artifactory) that your builds use.

Your builds keep listing only the repository manager, and get the SDKs through it like any other dependency.

## Verify what you download

Every jar, AAR and POM in the repository is signed with the ConfigDirector signing key. The signature is the `.asc` file next to each one.

- Fingerprint: `779A DCFB 334D A3FD 2E00 5AB4 3CD4 0757 E05C 6B4C`
- User ID: `ConfigDirector <opensource@configdirector.com>`
- Expires: 2028-08-20

The key is published on keys.openpgp.org and keyserver.ubuntu.com, and in full in the `KEYS.md` file of the [Android SDK](https://github.com/ConfigDirector/android-sdk/blob/main/KEYS.md) and [Java SDK](https://github.com/ConfigDirector/java-sdks/blob/main/KEYS.md) repositories.

### Gradle dependency verification

If your build verifies signatures with [Gradle's dependency verification](https://docs.gradle.org/current/userguide/dependency_verification.html), trust the key for the `com.configdirector` group by adding this entry to `<trusted-keys>` in `gradle/verification-metadata.xml`. Gradle downloads the key from the key servers above.

```xml
<trusted-key id="779ADCFB334DA3FD2E005AB43CD40757E05C6B4C" group="com.configdirector"/>
```

### gpg

Download a file and its signature, and check one against the other:

```bash
gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys 779ADCFB334DA3FD2E005AB43CD40757E05C6B4C
curl -O https://maven.configdirector.com/com/configdirector/server-sdk/1.11.0/server-sdk-1.11.0.jar
curl -O https://maven.configdirector.com/com/configdirector/server-sdk/1.11.0/server-sdk-1.11.0.jar.asc
gpg --verify server-sdk-1.11.0.jar.asc server-sdk-1.11.0.jar
```

Check that gpg reports a good signature and shows the fingerprint above.

### GitHub artifact attestations

Every jar, AAR and POM also has a GitHub artifact attestation, which records the SDK's source repository on GitHub and the release workflow run that built the file. Check a downloaded file with the [GitHub CLI](https://cli.github.com):

```bash
gh attestation verify server-sdk-1.11.0.jar --owner ConfigDirector
```

The command succeeds only when the file was built by a workflow in a ConfigDirector repository on GitHub.


## Sitemap

See the full [sitemap](https://docs.configdirector.com/sitemap.md) for all pages.
