Klever

In addition I suggest to move a common aspect path from a job description to to a rule specifications base. Anyway there is very pure means to change anything in rule specifications through job descriptions.

Common aspect should be choosed automatically between MAV and MPV.

Vitaly Mordan wrote:

Common aspect should be choosed automatically between MAV and MPV.

This feature request topic explicitly specifies that it is just for multi-aspect verification. Please, consider other issues separately to avoid unnecessary delays in implementing the primary ones.

Evgeny Novikov wrote:

Vitaly Mordan wrote:

Common aspect should be choosed automatically between MAV and MPV.

This feature request topic explicitly specifies that it is just for multi-aspect verification. Please, consider other issues separately to avoid unnecessary delays in implementing the primary ones.

Then what this issue is about?
MAV was implemented in master long ago.

Vitaly Mordan wrote:

Evgeny Novikov wrote:

Vitaly Mordan wrote:

Common aspect should be choosed automatically between MAV and MPV.

This feature request topic explicitly specifies that it is just for multi-aspect verification. Please, consider other issues separately to avoid unnecessary delays in implementing the primary ones.

Then what this issue is about?
MAV was implemented in master long ago.

But the blocking issue (#7392) isn't implemented and tested still. Without it using MAV is impossible in real production where nobody will specify some groups of rules to be checked together.