Konrad,
since the tool packages and deploys it is dependent Jackrabbit-Vault for
the package format and on Apache Sling and Composum for the
upload/install/list/uninstall/delete endpoint. I'd honestly much prefer
for it to be an Apache Sling module.
Ruben
On 7/17/2019 12:39 AM, Konrad Windszus wrote:
Hi Ruben,
very nice, but wouldn't it make more sense to contribute that to Apache Jackrabbit
(next to the https://github.com/apache/jackrabbit-filevault-package-maven-plugin
<https://github.com/apache/jackrabbit-filevault-package-maven-plugin>) rather
than to Sling?
AFAICS there is no dependency to Sling bundles but only to JCR...
WDYT?
Thanks,
Konrad
On 14. Jul 2019, at 17:44, Ruben Reusser <r...@headwire.com> wrote:
Dear Sling Developers,
in an effort to help 'front end developers' embrace Apache Sling and in order
to make simple front-end Sling projects maven independent we created a node
only slingpackager [1] and a sample VueJs based Slnig Content Browser [2] as a
showcase project.
We'd like to see the slingpackager (and potentially the showcase example) be
part of Apache Sling and maybe live on npmjs in an Apache Sling organization
(@apachesling for example).
We'd love to hear what you think about this!
Ruben Reusser
[1] https://github.com/peregrine-cms/slingpackager
[2] https://github.com/peregrine-cms/simple-sling-vue-example
