Priority: Not Evaluated
Affects Version/s: 4.2.0 Beta
Fix Version/s: None
I have a component B which depends on A and C.
A, B and C are root components meaning they can be selected individually in the UI.
When the user selects B, A and C are marked as requirements for installation (the column on right with the green dot).
However, when the installation is running, it seems that the components are installed in some order that does not reflect the dependency tree. A is installed, then B and then C.
It means that we can't create custom operations in B that would work on C files.
For the context, we have two individual products (A and C in this example), and one component that is the glue between the two products. The user can install them individually but could decide to install them as a whole system.
The installation step should trigger the installation of the components with no dependency first and resolve the order of the installation using the dependency tree.