It's useful to have an (integration) test that does little more than load the Spring context(s) and to have the logging configuration output the relevant Spring categories at the DEBUG level when you run it.
Build a man a fire, and he'll be warm for a day. Set a man on fire, and he'll be warm for the rest of his life.
The exception thrown by spring is very informative. You have to look at it closely, and you have to look at all of it. It is usually very long, and there are several "caused by" section. You have to go to the last caused by
Jayesh A Lalwani wrote:The exception thrown by spring is very informative. You have to look at it closely, and you have to look at all of it. It is usually very long, and there are several "caused by" section. You have to go to the last caused by
You see there are multiple caused by clauses. Usually, checking the last caused by gives you enough information to diagonose the issue. In the above case, the root cause is that a class wasn't found.