ProjectResolver: Sanitize error handling

There was lots of ad-hoc code dealing with errors, introduced by
different patches dealing with concrete bugs in an isolated manner.
Instead, we now use a structured approach that should reliably satisfy
the constraints of both command-line and IDE mode, handling errors only
on the project, product and group level.
The most visible effect of this is that we no longer run the risk of
emitting errors from disabled products, e.g. while evaluating properties
or file lists.

Change-Id: I0a27ff9d3f1f398d429c22d3ca2628b43f2e7879
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>

1 files changed, 1 insertions, 0 deletions

diff --git a/tests/auto/language/tst_language.h b/tests/auto/language/tst_language.h
index 9cf216360..c7520e9dc 100644
--- a/tests/auto/language/tst_language.h
+++ b/tests/auto/language/tst_language.h
@@ -92,6 +92,7 @@ private slots:
     void derivedSubProject();
     void enumerateProjectProperties();
     void environmentVariable();
+    void errorInDisabledProduct();
     void erroneousFiles_data();
     void erroneousFiles();
     void exports();