Now that Adobe donated the package creation goals of the content-package-maven-plugin to filevault-package-maven-plugin (http://jackrabbit.apache.org/filevault-package-maven-plugin/index.html) I am a bit unsure what advantages I get by building packages with wcm.io content package maven plugin (). The wiki page at https://wcm-io.atlassian.net/wiki/spaces/WCMIO/pages/50887164/Content+Package+Maven+Plugin+Comparison does not really point out the benefits and only lists some additional parametrization for certain goals. I would like to see a little text introduction hightlighting the main advantages of the wcm.io content package plugin.
In the best case any new features of the package goal would be contributed back to the official filevault-package-maven-plugin and everyone should be encouraged to use that one for building only.
If there are advantages of using the wcm.io plugin for the actual distribution of the packages, that should IMHO be also mentioned in http://jackrabbit.apache.org/filevault-package-maven-plugin/migrating.html.