Skip to content

Explain how custom repositories work with the build process #10437

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MarkvanMents merged 2 commits into from
Dec 4, 2025
Merged

Explain how custom repositories work with the build process #10437

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1fb81c8
Custom repositories and the build process
jdiehl Dec 2, 2025
98f46e4
Proofread
MarkvanMents Dec 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions ...t/en/docs/refguide/java-programming/managed-dependencies/custom-repositories.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,12 @@ This is also the recommended setup when there is limited or no access to the int
* **JFrog Artifactory** and **Sonatype Nexus** are popular tools that act as these "personal libraries." They can store your own libraries, and also "proxy" public repositories, meaning they download from the internet once and then serve it to everyone in your team from their local cache.
* **Local repository:** This is a folder on your network which contains your project dependencies. The folder can either follow the Maven-style layout or can be a simple folder containing your dependencies.

## Custom Repositories and the Build Process

When building Mendix applications in Mendix Cloud, dependencies are not downloaded. Instead, the build process relies on the dependencies being present in the `vendorlib` folder.

Studio Pro manages this by downloading dependencies from the configured repositories using Gradle and then committing the `vendorlib` folder to version control. When you set up a custom Gradle repository, this is used during the download phase, meaning all dependencies stored in vendorlib originate from that repository.

## How to Set up a Remote Repository

### Prerequisites
Expand Down