-
User Story
-
Resolution: Unresolved
-
P2: Important
-
None
-
QtGP 1.3
Why?
Cause
- Qt GP logs are cryptic and does not explain what is wrong
- Build does not stop to error
Customer
- From Qt hackathon participants and from my testing.
Cruft
- Why this would not be needed?
What?
One of the most common and repeating issues were to do with logs:
- Cryptic logs that are don’t explain what’s wrong (take C++ build fail due to a compile error).
- The user will have to hunt for the logs in the see of Gradle logs.
- Why doesn’t the build immediately stop when there’s an error?
As a first step to remedy this we should:
- Revise our code and make sure to return early in case of errors.
- Fail and warn early on about any missing tools, wrong values, etc.