Major changes in how the plugin acts & security improvements
2.0.0 is mostly about the plugin not doing things behind your back. Automatic updates can run when you save, when you open a project, before mvn clean install, or on a shortcut you pick, and every one of them asks before it touches a dependency. Turning auto update on or off for a dependency asks first as well. With "Update All" you can wave everything through at once, or go down the list and choose.
Reading and writing poms got a lot more careful. Dependencies that differ only by type or classifier are told apart properly now, and a version property shared between several dependencies no longer gets clobbered.
Templates can be saved straight from the form, or from the pom you already have. There is a new Template menu at the bottom of the window for saving the current pom.xml as a template, exporting it as xml, and importing an existing pom as one. The template picker moved up to sit right under the creation heading.
The rest is security and tidying up. Automatic actions respect IntelliJ Safe Mode, saved project data no longer carries absolute paths from your machine, and the plugin still only goes online when a feature actually needs it. Optional Maven downloads are checked against a pinned SHA-512 checksum and come with size limits, timeouts and temporary files that clean themselves up. The whole interface follows your active IntelliJ theme, custom ones included. On top of that there are a lot of fixes around concurrent updates, builds, notifications and pom edits.