Clarify differences towards filevault-package-maven-plugin
Description
Gliffy Diagrams
Activity
Stefan Seifert November 27, 2017 at 5:43 PM
done - documentation is updated: http://wcm.io/tooling/maven/plugins/wcmio-content-package-maven-plugin/
additionally i've deprecated the "package" goal of the wcm.io content package maven plugin and published a migration guide to filevault-package-maven-plugin: https://wcm-io.atlassian.net/wiki/x/GYB1BQ
for the delta that the filevault-package-maven-plugin does not support yet i've opened issues at jackrabbit and hope they will be accepted:
JCRVLT-239 Package Maven Plugin: Add "acHandling" property
JCRVLT-240 Package Maven Plugin: Support for package thumbnails
Stefan Seifert November 17, 2017 at 12:54 PM
well, at the time of https://wcm-io.atlassian.net/browse/WTOOL-31#icft=WTOOL-31 the filevault-package-maven-plugin was not available and we were not aware that the jackrabbit project finally got a contribution for this (which was long overdue).
concerning the building of packages our goal is indeed to provide a migration path to filevault-package-maven-plugin and contribute missing or better features from our plugin there. we've not startet this, but it's on our todo list.
what the wcm.io content package plugin still makes unique is it's support for uploading and download packages to AEM package manager and composum console. the adobe plugin can upload to adobe package manger as well, but the wcm.io plugin is much more sophisticated and fault-tolerant for this as it is required to be used for deployment automation (e.g. with CONGA ans Ansible).
we will look into improving the documentation on this and start thinking about the migration path to filevault-package-maven-plugin in the next few weeks.
Details
Details
Assignee
Reporter
Components
Affects versions
Priority
Major
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 (https://wcm-io.atlassian.net/browse/WTOOL-31#icft=WTOOL-31). 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.