Task #36562
"Compile run failed" output is confusing
| Status: | Resolved | Start date: | 2012-04-25 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Robert Lemke | % Done: | 100% |
|
| Category: | Core | |||
| Target version: | TYPO3 Flow Base Distribution - 1.1 | |||
| Sprint: | Has patch: | No | ||
| PHP Version: | Complexity: |
Description
The exception thrown on a failed compile run produces quite confusing, verbose output without any benefit.
Associated revisions
[TASK] Improve "compilation error message"
When the compile run failed, an exception was thrown until now. This
lead to confusing output. With this change it doesn't output useless
PHP version info etc. anymore.
Change-Id: Ic621e3bf5d6dbfdbe98c53e50b94a9e6b6cdfd74
Resolves: #36562
Releases: 1.1
History
#1 Updated by Karsten Dambekalns over 3 years ago
- Status changed from New to Accepted
#2 Updated by Gerrit Code Review over 3 years ago
- Status changed from Accepted to Under Review
Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/10761
#3 Updated by Karsten Dambekalns over 3 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 9539aca721deb3bfb54c6188612e9e3e0f923856.
#4 Updated by Henrik Møller Rasmussen over 2 years ago
Would it be possible to improve the error message on compile run errors?
A couple of times I have been getting cryptic errors from the compile run, with no info about where to start searching for the problem. There is no info in the log either.
It have happened on syntax errors and on use of non-existing classes. Fx. I extended a class from a package that was not installed on the production system.