CUBA Studio Server window contains a field where you can select an artifact repository. By default, it contains two entries:

Both repositories have identical contents for the latest platform versions. We assume that Bintray is more reliable for worldwide access.

When you create a new project in CUBA Studio, it’s build.gradle contains the link to the repository which is selected in the Studio server window. In case of Bintray, the build script is also configured to use Maven Central, JCenter and Vaadin Add-ons repositories separately.

If your project uses CUBA Premium Add-ons, Studio adds one more repository:

Both Premium Add-ons repositories require a user name and a password which are provided by per-developer subscription. The first part of your license key before dash is the repository user name, the part after dash is the password. For example, if your key is 111111222222-abcdefabcdef, then the user name is 111111222222 and the password is abcdefabcdef.

When you build the project from Studio, it passes repository credentials to Gradle automatically. If you want to build the project outside Studio, you can pass premiumRepoUser and premiumRepoPass in the command line arguments with -P prefix. In case of Bintray, the user name must be followed by @cuba-platform.

Example of building with repo.cuba-platform.com:

Example of building with Bintray:

Instead of passing credentials each time you build the project from the command line, you can once set the following environment variables: