6.2 Profile Inheritance

One profile can extend one or many different parent profiles. To define profile inheritance you can modify the build.gradle of a profile and define the profile dependences. For example typically you want to extend the base profile:

dependencies {
    runtime project(':base')
}

By inheriting from a parent profile you get the following benefits:

• When the create-app command is executed the parent profile’s skeleton is copied first

• Dependencies and build.gradle is merged from the parent(s)

• The application.yml file is merged from the parent(s)

• CLI commands from the parent profile are inherited

• Features from the parent profile are inherited

To define the order of inheritance ensure that your dependencies are declared in the correct order. For example:

dependencies {
    runtime project(':plugin')
    runtime project(':web')
}

In the above snippet the skeleton from the "plugin" profile is copied first, followed by the "web" profile. In addition, the "web" profile overrides commands from the "plugin" profile, whilst if the dependency order was reversed the "plugin" profile would override the "web" profile.