Simon Willnauer 9506f60504 Improve error message if a setting is not found (#18920) ... Today we only emit that the setting wasn't found unless we have some DYM suggestions. Yet, if a setting is not found at all and there are no suggestions due to typos it's likely a removed setting or the plugin that is supposed to be configured is not installed. This commit adds some info text to the exception to help the user debugging the problem before opening bugreports. Instead of emitting: `unknown setting [foo.bar]` we now emit: `unknown setting [foo.bar] please check the migration guide for removed settings and ensure that the plugin you are configuring is installed` Relates to #18663		2016-06-20 13:10:35 +02:00
..
src	Improve error message if a setting is not found (#18920)	2016-06-20 13:10:35 +02:00
.gitignore	Build: Add fake project to include buildSrc as normal project	2016-05-06 22:26:15 -07:00
build.gradle	Update forbiddenapis to 2.2 and fix painless tests	2016-06-19 20:40:38 +02:00
version.properties	Upgrade to Lucene 6.1.0. #18926	2016-06-17 09:03:00 +02:00