There can be any number of application components, but they are processed in a strict component order. This order determines the priority that will be given to artifacts that share the same name but appear in different components. This is fundamental to the manner in which Cúram web client applications are customized.
The component order is defined by the CLIENT_COMPONENT_ORDER environment variable. This is a comma-separated list of component names. Use only commas; do not use spaces. You must place the component with the highest-priority first in the list and continue in descending order of priority. The core component always has the lowest priority and is implicitly assumed to be at the end of the list; you do not need to add it explicitly.
For example, setting the component order to "MyComponentOne,MyComponentTwo" will give the highest priority to artifacts in the MyComponentOne folder within <client-dir>/components, a lower priority to artifacts in the MyComponentTwo folder, and the lowest priority to artifacts in the core folder. Any component folder not listed in the component order will not be included in the build and a warning will be displayed to indicate that these components have been ignored. If you do not set the component order at all, the default component order will include all components in alphabetical order.