Hi Andreas, On Fri, 2019-11-08 at 09:51 -0800, Andreas Schaefer wrote: > Hi > > I am wondering how a Sling FM Starter Module would look like and how > it is used by clients like Peregrine. > > It is my assumption that any FM slingosgifeature project will install > that file on release on a public Maven repository like all of our > Sling Module. > > Then the Sling FM Starter Module will select the appropriate > slingosgifeature files and assemble it into a Sling release > slingosgifeature which is then also installed on a public Maven repo. > This enables anyone to build the latest Sling instance w/o having any > other Sling Module checked out / built like right now it is done in > PM based Sling Starter. > > A customer will then do the same by taking the Sling slingosgifeature > file and assembly it with their own project and external projects > slingosgifeature files to build the final Sling / Customer instance.
Overall that sounds reasonable to me. The only note that I want to make is that since we are doing releases at best once per year, downstream projects would either need to depend on SNAPSHOT versions of the Sling Starter, or depend on older versions. Thanks, Robert
