[
https://issues.apache.org/jira/browse/SLING-6081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15535853#comment-15535853
]
Stefan Seifert commented on SLING-6081:
---------------------------------------
in the mail thread there was a discussion about simplifying the package
creation handling compared to what the adobe content package plugin currently
supports, like starting with a 95% solution.
this is possible for the start, but we should make design decisions which makes
it hard to add the missing 5% features later on - i assume over time we need to
support all packaging special features.
> Sling Content Package Maven Plugin
> ----------------------------------
>
> Key: SLING-6081
> URL: https://issues.apache.org/jira/browse/SLING-6081
> Project: Sling
> Issue Type: New Feature
> Components: Maven Plugins and Archetypes
> Reporter: Stefan Seifert
>
> in this mail thread better support for resource/content packaging was
> discussed: http://sling.markmail.org/message/m2xfrnljzhqnfbpc
> part of this is having a open source alternative for the [adobe content
> package maven
> plugin|https://repo.adobe.com/nexus/content/groups/public/com/day/jcr/vault/content-package-maven-plugin/]
> in sling.
> a good starting point for this may be the wcm.io content package maven plugin:
> * http://wcm.io/tooling/maven/plugins/wcmio-content-package-maven-plugin/
> *
> https://github.com/wcm-io/wcm-io-tooling/tree/develop/maven/plugins/wcmio-content-package-maven-plugin
> which i would be happy to contribute to sling. it also supports good and
> production-proven support for uploading and downloading packages (and tries
> to use plugin configuration as near to the adobe plugin as possible).
> the only thing to add is support for creating the file vault package zip from
> the project files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
