# Publish Maven artifacts to CloudRepo > Publish a Maven artifact to a CloudRepo repository with mvn deploy and a repository token, check that it landed, republish snapshots, and fix a 401, 403, 409 or 413. Maven publishes to CloudRepo like it publishes to any repository: the repository’s address goes in `pom.xml`, the credential goes in `settings.xml`, and `mvn deploy` uploads your artifact. This page is for the person who publishes a build. To use what you published, see [Maven repositories](/docs/formats/maven.html). ## Before you start - A Maven repository. If you have none, [create one](/docs/manage/repositories.html#creating-a-repository). - A repository token that reaches it, with **Read + write**. A **Read only** token can pull but not publish: CloudRepo answers its `mvn deploy` with `403`. See [Repository tokens](/docs/authenticate/repository-tokens.html) to create one. Your username is the email address of the account that created the token, and your password is the token. - Your repository’s URL, `https://.mycloudrepo.io/repositories/`. Your organization’s name is the first part of your CloudRepo host, and the repository’s name is the one the admin portal shows. The repository’s [Connection Settings](/docs/manage/repositories.html#view-connection-settings) show the URL with your names filled in. ## Publish with mvn deploy **Maven** **1. Put the credential in `~/.m2/settings.xml`.** The `` is a name you choose, and the repository in your `pom.xml` must use the same one. `${env.CLOUDREPO_TOKEN}` reads the token from an environment variable, so the file holds no token. Export the variable in the shell that runs Maven, or in your CI’s secret store. `~/.m2/settings.xml` ```xml cloudrepo you@example.com ${env.CLOUDREPO_TOKEN} ``` **2. Name the repository in `pom.xml`.** The `` repository is where `mvn deploy` publishes. Put it in a parent POM if you have one, so a project states it once. `pom.xml` ```xml cloudrepo https://your-org.mycloudrepo.io/repositories/your-repo ``` **3. Publish.** Run this in the directory of your `pom.xml`: **Terminal** ```bash mvn --batch-mode deploy ``` Expected: Maven prints `Uploading to cloudrepo:` and `Uploaded to cloudrepo:` for the POM, the JAR and `maven-metadata.xml`, and ends with `BUILD SUCCESS`. **4. Check that it landed.** Fetch the POM you published. Put the credential in `~/.netrc` and ask curl to read it, and keep the file readable by you alone (`chmod 600 ~/.netrc`). `~/.netrc` ```ini machine your-org.mycloudrepo.io login you@example.com password YOUR_REPOSITORY_TOKEN ``` **Terminal** ```bash curl --netrc --fail --output docs-maven-1.0.0.pom \ https://your-org.mycloudrepo.io/repositories/your-repo/com/example/docs/docs-maven/1.0.0/docs-maven-1.0.0.pom ``` The path under the repository URL is your artifact’s group (dots become slashes), its name, its version and the file. The artifact is also listed in the repository in the [admin portal](https://admin.cloudrepo.io). ![The maven-releases file browser at com/example/docs/docs-maven/1.0.0: docs-maven-1.0.0.jar and docs-maven-1.0.0.pom, with their checksum files.](/docs/_astro/shots/publish-maven/1-file-list.981bb1d21fcef35a.png) ## Snapshots and releases A version that ends in `-SNAPSHOT` can be published again and again, so your CI can deploy each build. A release version, one that does not end in `-SNAPSHOT`, is published once: CloudRepo refuses a second publish to the same coordinate with `409`, and the artifact already there stays as it is. Maven rewrites `maven-metadata.xml` and its checksum files on every publish, so the refusal does not apply to them. The setting behind this, Overwrite Protection, is on by default; see [Overwrite Protection](/docs/manage/repositories.html#overwrite-protection). ## When a publish is refused Maven prints only the status line, such as `status code: 409, reason phrase: Conflict (409)`, and not the explanation CloudRepo sends with it. Check these in order: - **401 Unauthorized.** The credential was refused. The username must be the email address of the account that created the token, and the password the token itself. A token that is expired or revoked fails the same way: the **Repository Tokens** page in the admin portal shows its status. - **403 Forbidden.** The token cannot publish here. A **Read only** token cannot publish at all, and a token reaches only the repositories ticked when it was created. Use a **Read + write** token that includes this repository. - **409 Conflict.** You published a release version that is already in the repository. Nothing is broken: CloudRepo refuses to replace a release on purpose. Publish a new version, or use a `-SNAPSHOT` version while you iterate. If the repository is meant to accept republished releases, turn **Overwrite Protection** off in its settings, knowing that a build that resolved that version yesterday can then get different bytes today. - **413 Request Entity Too Large.** One file is over 50 GB (50,000,000,000 bytes), the most a single file can be. More: [Repository tokens](/docs/authenticate/repository-tokens.html), for every client’s credential; [Publish Gradle artifacts](/docs/publish/gradle.html), if Gradle builds your project; and [Maven repositories](/docs/formats/maven.html), for resolving dependencies and proxies. --- The page: https://www.cloudrepo.io/docs/publish/maven.html