Talking with someone at SpringOne about the problems with telling what auto-configuration is doing and we had the idea of an auto-configuration report over time. The idea is that each run of an application saves a version of the report. When there's an issue or something unexpected happens it would be possible to compare with a previous run and see what's different.
The key feature would be the difference between two reports. Hopefully making them easier to understand.
Comment From: snicoll
Can we attempt to store the classpath as well? Since libraries follow a naming convention (artifactId-version[-scope]) we could relatively easily detect new libraries. Also, upgrading to a new version might bring new transitive dependencies that could break things...
Comment From: wilkinsona
DevTools has support for this now, but there's no diff produced across JVM restarts. We should use this issue to add that functionality.