> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/developer-tools/integrations/snyk-ide-plugins-and-extensions/troubleshooting-ides/maven-scans-with-private-repositories.md).

# Maven scans with private repositories

How to resolve Maven scan failures caused by private repository dependencies in IDE plugins

## Problem <a href="#problem" id="problem"></a>

Maven fails due to dependencies that reference private repositories in Ithe IDE plugin or CI/CD pipeline.

## Investigation <a href="#investigation" id="investigation"></a>

* Try running CLI standalone with the repository.
* Check to see if Maven profiles or Maven settings are used for running the build (for example, located in `.mvn` ).
* Check to see if the pipeline has access to the private sources.

Dependencies need to be downloaded from a private repository and the Snyk CLI shows that the download fails in the error message.

## Solution <a href="#solution" id="solution"></a>

You can establish Maven settings or a profile containing the connection information, for example, with `-- -s your-home-directory/.m2/settings.xml` or `-- -Dprofile=my-profile`.

These parameters can be passed on to the CLI using the `Additional Parameters` plugin setting in IDE. For CI/CDs. this should be passed as a pipeline argument if the Snyk CLI used directly, or a correct path mapping should be provided, if run in Docker image.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snyk.io/developer-tools/integrations/snyk-ide-plugins-and-extensions/troubleshooting-ides/maven-scans-with-private-repositories.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.