Create a new project in Studio and specify the following properties on the New project screen:

Edit Project properties and on the Advanced tab, set the Module prefix to cust. This is necessary to assemble component artifacts with names different from the default app.

Create the Customer entity with at least the name attribute. Switch to the Instance name tab and specify add name to the name pattern attributes.

Generate DB scripts and create standard screens for the Customer entity: cust$Customer.browse and cust$Customer.edit. After that, go to main menu designer and rename the application menu item to customerManagement.

Click to the App component descriptor link on the Project properties panel. Save the generated descriptor by clicking OK.

Test the Customer Management functionality: Run > Create database, Run > Start application server, then open http://localhost:8080/cust in your web browser.

Install the application component into the local Maven repository by executing the Run > Install app component menu command.

Create a new project in Studio and specify the following properties on the New project screen:

Edit Project properties and on the App components panel click the plus button next to Custom components. In the Custom application component dialog, select the customers project in the Registered project drop-down list. The list contains all project registered in Studio that have an app-component.xml descriptor. Click OK in the dialog. The Maven coordinates of the Customer Management component will appear in the list of custom components. Save the project properties by clicking OK.

Create the Order entity and add the date and amount attributes. Then add the customer attribute as a many-to-one association with the Customer entity - it should be available in the Type drop-down list.

Generate DB scripts and create standard screens for the Order entity. When creating standard screens, create a order-with-customer-view view that includes the customer attribute and use it for the screens.

Test the application functionality: Run > Create database, Run > Start application server, then open http://localhost:8080/app in your web browser. The application will contain two top level menu items: Customer Management and Application with the corresponding functionality.

Open the customers project in Studio.

Edit the Customer entity and add the address attribute. When saving the entity, select both browser and editor screens to include the new attribute.

Generate DB scripts - a script for altering table will be created. Save the scripts.

Test the changes in the component: Run > Update database, Run > Start application server, then open http://localhost:8080/cust in your web browser.

Re-install the application component into the local Maven repository by executing the Run > Install app component menu command.

Close the customers project and open sales.

Execute Build > Clean, then Build > Assemble project menu commands.

Execute Run > Update database - the update script from the Customer Management component will be executed.

Execute Run > Start application server and open http://localhost:8080/app in your web browser - the application will contain the Customer entity and screens with the new address attribute.

Stop the Studio server.

Set up a repository and make it a proxy for the public CUBA repository https://repo.cuba-platform.com/content/groups/work.

Open build.gradle of the customers project in a text editor. Replace the repository and its credentials in buildscript/repositories section and add the uploadRepository to the cuba section:

buildscript {
    ...
    repositories {
        maven {
            url 'http://repo.company.com/nexus/content/groups/work' // repository containing CUBA and your own artifacts
            credentials {
                username(rootProject.hasProperty('repoUser') ? rootProject['repoUser'] : 'admin')
                password(rootProject.hasProperty('repoPass') ? rootProject['repoPass'] : 'admin123')
            }
        }
...
cuba {
    ...
    uploadRepository {
        url = 'http://repo.company.com/nexus/content/repositories/snapshots' // repository for uploading your artifacts
        user = 'admin'
        password = 'admin123'
    }
}

Open the command line and run gradle assemble in the customers project root directory. This ensures your new repository caches CUBA artifacts required for working in Studio.

In the Studio server window, specify your repository and credentials instead of the standard CUBA repository. Start the Studio server.

Open the customers project in Studio.

In the Studio Search dialog (Alt-/), find the uploadArchives Gradle task and run it. You can also run this task from the command line. The Customer Management component artifacts will be uploaded to your repository.

Remove the component artifacts from your local Maven repository to ensure that they will be downloaded from the remote repository when the sales application is assembled the next time: just delete the .m2/repository/com/company folder located in your user home directory.

Open the customers project in Studio. The repository URL in its build.gradle will be automatically changed to the one specified in the Studio server window.

Now you can assemble and run the application - the Customer Management component will be downloaded from the remote repository.