Bukkit/Bukkit — comment on commit 55f405f4a855fcf165e02379cae5bebc76c517d4
File:  line 0
By desht:

There are some nasty problems with this API, and I really don't think it should have been dropped on plugin devs without a little more prior warning and discussion, especially given that the current API has been deprecated.

* No attempt to maintain any kind of compatibility, gratuitous renaming of methods, classes, etc.

* getList() is returning null for keys I know exist, and are lists in my YAML config file (where getStringList() worked fine before)

* It used to be possible to set a HashMap as a value of a Configuration - e.g. config.set("somekey", map) worked fine. Now it throws an IllegalArgumentException (unsupported class)

* plugin.getConfiguration() returns a FileConfiguration object. Why not a YamlConfiguration object? config.yml is still a YAML file, right?

* Even though you can use plugin.getConfiguration() to get the plugin's configuration without a filename, as far as I can see, you still need to explicitly create and pass a File object if you later need to save or reload the plugin's configuration. That's just ugly.