On Thu, 2020-03-26 at 15:48 +0100, Carsten Ziegeler wrote: > On 26.03.2020 15:12, Robert Munteanu wrote: > > Well, if we ask users to download only one artifact and the other > > is > > downloaded on-demand, then the situation is mostly the same IMO. > > > Oh, I see, now I get what you are saying. Yes, that's true > > We could also provide a shell script for download which downloads N > artifacts :) Sounds like a joke, but in reality you need at least > the > launcher, an OSGi framework, and a feature archive. Maybe some > extensions for the launcher, too.
I actually started writing that we need a script, but decided against it, but if I'm not the only one thinking about it, maybe there's some value it in. Karaf (and probably others) have a couple of helper scripts, and we might consider that as well, with a zip structure such as: bin/ \- sling.sh \- sling.bat launcher/ \- launcher.jar \- framework.jar features/ \- feature-a.zip \- feature-b.zip \- feature-c.zip Of course, that is something for a second step. You mentioned n feature files. In this feature archive scenario, do you still see the features generated from the starter or would they be moved somewhere else? Thanks, Robert
