**Source URL:** https://general.veevavault.dev/sitevault/vault-sdk/developing-code/pom-setup.md

# POM Setup



The artifacts (`.jars`) for the Vault Java SDK are distributed by a Maven Repository Manager. This allows you to easily download the Vault Java SDK and all its dependent libraries by simply setting up a Maven project pointing to the Maven Repo Manager in the `pom.xml` file.

This file has three sections you may need to edit:

* `<properties>`

* `<repositories>`

* `<dependencies>`

## Properties {#properties}

The `<vault.sdk.version>` in your POM file must match the version of the Vault you are developing on. Note that when developing on limited release Vaults, the Vault Java SDK feature set is <span class="label label-warning">Beta</span> and subject to change.

When Vault is upgraded to a new release or if you're switching between Vaults during development, the `<vault.sdk.version>` element in the properties section must be updated accordingly to reimport the correct version of the Vault Java SDK from the repository.

You can find your Vault version in **Admin > Settings > General Settings**. You don't need to worry about your Vault's build number.

The `<vault.sdk.version>` must be in the following format:

`[`{vault_version}`-release0, `{vault_version}`-release1000000]`

* ``{vault_version}``: Your Vault version, using only periods (`.`) and not the letter R.

For example, a Vault on version 26R1.0 should look like this:

```
<properties>
    <vault.sdk.version>[26.1.0-release0, 26.1.0-release1000000]</vault.sdk.version>
</properties>

```

## Repositories {#repositories}

Your `<repositories>` section should look like this:

```
<repositories>
    <repository>
        <id>veevavault</id>
        <url>https://repo.veevavault.com/maven</url>
        <releases>
            <enabled>true</enabled>
            <updatePolicy>always</updatePolicy>
        </releases>
    </repository>
</repositories>

```

## Dependencies {#dependencies}

This dependency will pull the Vault Java SDK and all the libraries it depends on from the repository, and allows you to connect to the [debugger](/vault-sdk/sdk-debugger/debugger-setup/).

Your `<dependencies>` section should look like this:

```
<dependencies>
    <dependency>
        <groupId>com.veeva.vault.sdk</groupId>
        <artifactId>vault-sdk</artifactId>
        <version>${vault.sdk.version}</version>
    </dependency>
    <dependency>
        <groupId>com.veeva.vault.sdk.debugger</groupId>
        <artifactId>vault-sdk-debugger</artifactId>
        <version>${vault.sdk.version}</version>
    </dependency>
</dependencies>

```

<SiteConditional sites="qualityone" id="qualityone-qms-sdk"></SiteConditional>



---

**Previous:** [Developing Code](/sitevault/vault-sdk/developing-code)  
**Next:** [Programming Guidelines](/sitevault/vault-sdk/developing-code/programming-guidelines)