Hi Ruben,
On 26.03.2020 12:51, [email protected] wrote:
Carsten,
If I remember this correctly Andreas wrote the kickstarter to wrap the launcher
and make it controllable (eg start, stop, use in it tests).
Correct - and that is useful work.While we discussed that approach we
also set, that we still want something easy, someone probably new to
Sling can just download and run. You don't want that its required to
install maven, setup a project etc just to get something running and
have a look at it.
Feature archives as a concept are independent from this; but we need a
format that allows to distribute a feature together with referenced
artifacts as a single package. We discussed that some time back and have
support for it since some time. All that is missing is being able to
launch these directly.
Do you mind also pointing to the documentation of the archive zip format? I am
hoping that format is just a .m2 repo structure that can be mounted like a
local maven repository and used by the launcher. An approach like this would
make it transparent to the developer how the archive is structured and consumed.
I think other than the javadoc of the code which does it, we don't have
documentation. But yes, it is a zip file using a maven repository
structure with a special Manifest to identify which features should be
used for this archive.
I'd also love to understand more on how the archives are assembled
We have support in the slingfeature-maven-plugin for some time.
https://github.com/apache/sling-slingfeature-maven-plugin#create-feature-archives-attach-featurearchives
which is the most convenient way to create them today.
Regards
Carsten
Thank you
Ruben
-----Original Message-----
From: Robert Munteanu <[email protected]>
Sent: Thursday, March 26, 2020 4:38 AM
To: [email protected]
Subject: Re: [RT] Feature archives, launcher and Sling Starter
Hi Carsten,
On Wed, 2020-03-25 at 10:21 +0100, Carsten Ziegeler wrote:
Add this point I'm a little bit unsure which way to go with the
starter, therefore asking for feedback. I'm currently leaning towards
the second
option: just creating a feature archive for the starter (which we can
already do today)
I am not 100% sure I get the difference. With the 'classic' starter, we would
produce a single, fat, jar that contains everything.
What would be the proposal for the feature archive based jar? Do we ask the
users to download a launcher jar and then run a command similar to
$ java -jar launcher.jar --feature-archive=https://maven/repo/archive.zip?
I assume the option is there to also load a feature archive from the local
disk, so that the launcher can work with requiring any network access as well.
Thanks,
Robert
--
--
Carsten Ziegeler
Adobe Research Switzerland
[email protected]
