This was useful when plugins first started upgrading to uuid because each
plugin would implement their own way for grabbing uuid's from mojang. Because
none of them shared the result they would quickly hit the limits on the api
causing the conversion to either fail or pause for long periods of time. The
global api cache was a (very hacky) way to force all plugins to share a cache
but caused a few issues with plugins that expected a full implementation of
the HTTPURLConnection. Due to the fact that most servers/plugins have updated
now it seems to be a good time to remove this as its usefulness mostly has
expired.
When on Java 7 we can register the classloader as parallel capable to prevent deadlocks caused by certain scenarios. Due to the nature of PluginClassLoader this isn't completely safe, but we can make it safer by switching to concurrency focused collections. Either way this is far better than crashing the server.
* Now Tracks Commands
* Resolved Performance issue with Bukkit HandlerList method. Now all timings simply uses the Spigot System
* Performance Improvement simply not using TimedRegisteredListener too
* Bug with SyncChunkLoad tracking resolved. Now properly tracks many aspects of sync chunk load.
* Reset/On/Off accuracy - should no longer have any issues turning it on/off during runtime, so this has been re-enabled.
* Paste command on RCON now works
* Now tracks everything related to plugins too, so you can easily see total plugin cost
* Now tracks Tasks better and where they came from
* Now tracks plugins event handlers to the Listener/Method name too.
* Merged some Bukkit Patches so all timings changes are in 1 patch.
* Moved back to a CLQ for CustomTimingsHandler for thread safety for when tasks are created Async but then executed sync.
Whilst it is possible for a change such as this to be breaking, the version bump in itself is very small and Guava only removes APIs after 18 months deprecation. Given the proliferation of servers such as MCPC bundling Guava versions of 14.0 upwards as well as the fact that developers should steer clear away from using deprecated APIs, it is very unlikely this change will cause any issues. Furthermore this version brings multiple bug fixes and represents the minimum version required by Minecraft itself.
