There was a more general CONTROLLER-922 which was fixed for syntactic errors.
There is a CONTROLLER-1349 concerning with a side effect of config subsystem stopping on semantic error, which was postponed to Beryllium.
This improvement concerns with question of reporting semantic errors, which would be nice to have in Lithium.

Steps to reproduce: As in CONTROLLER-1349 with the alternative step 11.

On current Lithium, there is no message (at level INFO or higher) which would inform the user that config-stopping error has even happened.
It would be better to have a log message specifying which feature/configfile/module/element contains the semantic error.