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). 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'd also love to understand more on how the archives are assembled 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
