asofold 1f0aafb63e Add a fail for null-worlds on updating set-back locations internally. ... Setting a set-back location with a null World will now lead to a NullPointerException. Setting null worlds on set-back locations is not intended by contract, however due to using temporary Location instances with Entity.getLocation(Location) and setting the world to null afterwards to prevent memory leaks, also considering the number of places where setSetBack is used, this seems to be an appropriate measure to track better or help excluding violations of that contract.		2014-04-12 20:31:03 +02:00
..
src	Add a fail for null-worlds on updating set-back locations internally.	2014-04-12 20:31:03 +02:00
pom.xml	Set dependencies to current snapshots.	2014-02-16 21:49:33 +01:00