Diagnostic of configuration inconsistency could be better

JavaTest silently ignores some inconsistencies in configuration. Simple scenario:
- configure a test suite with an Exclude list file specified
- exit JavaTest
- remove (move) .jtx file
- start JT (previous configuration is restored without any warnings)
- run tests (tests are executed in spite of .jtx is missing)

The only way to see inconsistency is to open Exclude List interview. In this case JT won't allow to close the dialog unless the inconsistency is fixed.

Perhaps, some mechanism to alarm user if something wrong with interview could be helpful. Exclude List is just partial case...