In v3.0.0 of the plugin the useReleaseProfile parameter has been deprecated (and default value changed to false).
This effectively changes from convention over configuration with a default release profile (the release-profile profile in the super-POM) so that the end user now needs:
1. to create a release profile (with his own naming choice)
2. and configure the plugin to use it (like add <arguments>-Pname_of_the_release_profile ...</arguments>).
We need to document this change in behavior as well as describe best-practice for handling this.