Hi,
I also have my doubts... reasoning to have it in Sling from [2]:
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.
Composum [3] is included in the sling starter but not actually
maintained
as part of Sling. I'm not aware of any dependency the packager would
have
to Sling, so I think the Jackrabbit project would make a lot more sense
to
host the Packager tool. For instance, people not using Sling but only
Jackrabbit could use it, also maybe at some point somebody will
eventually
create an Open Source Package Manager there (to provide the simple
endpoints
for upload/install/list/uninstall/delete without UI would be actually
really
easy, maybe it's a good time to do this now :)
-Georg
[3] https://github.com/ist-dresden/composum
On 2019-08-27 11:04, Robert Munteanu wrote:
Hi Stefan,
On Tue, 2019-08-27 at 08:49 +0000, Stefan Seifert wrote:
i'm not against adding it to sling, but maybe the jackrabbit project
would also be a good place for it? alongside with [1]?
This was (summarily) discussed at [2]. Don't have a strong opinion
either way, just relaying the answer :-)
Thanks,
Robert
stefan
[1] http://jackrabbit.apache.org/filevault-package-maven-plugin/
[2]:
https://lists.apache.org/thread.html/8e417968d0b4ecaa3eb3bd321b13629b86f59c5e2b20284f138119b0@%3Cdev.sling.apache.org%3E
> -----Original Message-----
> From: Robert Munteanu <romb...@apache.org>
> Sent: Monday, August 26, 2019 4:43 PM
> To: dev@sling.apache.org
> Subject: [VOTE] Accept the donation of the Sling Packager tool,
> SLING-8584
>
> Hi,
>
> Please vote to accept the donation of the Sling Packager module
> described in SLING-8584 [1].
>
> This majority vote is open for at least 72 hours.
>
> Thanks,
>
> Robert
>
> [1]: https://issues.apache.org/jira/browse/SLING-8584
>
