On Sat, 2016-10-01 at 13:43 +0200, Konrad Windszus wrote:
> What about an HTTP API to list, download, upload/install and build
> packages? I guess the installer factory would only cover the
> upload/install part of it.
I think this is a good idea, but should probably tackled in a follow-up
task,
What about an HTTP API to list, download, upload/install and build packages? I
guess the installer factory would only cover the upload/install part of it.
> Am 30.09.2016 um 14:25 schrieb Carsten Ziegeler :
>
> Stefan Seifert wrote
>> i've created a new ticket for further
Stefan Seifert wrote
> i've created a new ticket for further discussion about a "sling content
> package plugin"
> https://issues.apache.org/jira/browse/SLING-6081
>
> open in this thread is the "receiver part" to deploy content packages on
> sling instances which is currently not possible
rdparty applications.
stefan
>-Original Message-
>From: Robert Munteanu [mailto:romb...@apache.org]
>Sent: Friday, September 30, 2016 12:19 PM
>To: dev@sling.apache.org
>Subject: Re: Resource packaging/content packaging in Sling
>
>On Fri, 2016-09-30 at 10:16 +0200, Carsten
On Fri, 2016-09-30 at 10:16 +0200, Carsten Ziegeler wrote:
> Robert Munteanu wrote
> > On Wed, 2016-09-28 at 21:49 +, Stefan Seifert wrote:
> > > wcm.io also has a content package plugin [4] which already
> > > replaces
> > > parts oft he adobe content package maven plugin (upload/download
> >
Robert Munteanu wrote
> On Wed, 2016-09-28 at 21:49 +, Stefan Seifert wrote:
>> wcm.io also has a content package plugin [4] which already replaces
>> parts oft he adobe content package maven plugin (upload/download
>> package part), but not yet the part building the ZIP package from the
>>
On Wed, 2016-09-28 at 21:49 +, Stefan Seifert wrote:
> wcm.io also has a content package plugin [4] which already replaces
> parts oft he adobe content package maven plugin (upload/download
> package part), but not yet the part building the ZIP package from the
> VLT file layout. it could be
I currently solve it by using the package manager from composum[2] but having
support for content packages in Sling itself would in my opinion create extra
opportunities.
There are for example occasions where developers make something for AEM which
could just as well work in standard Sling.
discussed at the Sling Committer Round Table @ adaptTo() 2016
currently there is no support for content packages in sling to easily package
content/resources from the repository or resource hierarchy and transfer it
between instances.
concerning File Vault packages several parts are already