Hi Andy
I did face a similar challenge and we added the magic ${{filename}}
placeholder which is replacing with the inputfilename (w/o the .zip
extension)
The converter now also takes 1..n packages as input which it processes
after ordering them to be able to extract service users and their ACL setup
into repoinit statements (the ordering by dependency happens to be able to
find/detect the service users before the acls as only those are currently
processed in repoinit - groups and normal users have further challenges
like group memberships and acl inheritance which is why at least acl
processing for those doesn’t match exactly with what repoinit allows.
Anyhow service users are s fundamental precondition for code to act at all
and in contrast to groups are a must have at repository startup - as in
composite nodestorescenarios the content outside of apps smd libs might be
changes ‚later‘ repoinit sounded like the right choice to guarantee this
tho be processed.
I hope this clarifies the latest changes applied by Simo.
Cheers
Dominik
Andreas Schaefer <schaef...@me.com.invalid> schrieb am Mi. 8. Mai 2019 um
00:59:
> Hi
>
> I am working on migrating a multi-package project from a traditional Sling
> deployment to a feature model based system. What I want to do is to launch
> the project and Sling together into a full fledge application using the
> converted FM models together with the Sling FM models.
>
> In order to deploy through the Feature Model Launcher the group and the
> artifact need to be the same in all the FM models.
>
> For my Sling conversion which I also will use here to setup Sling I use I
> am going to use an Model ID like this:
>
>
> "${project.groupId}:${project.artifactId}:slingosgifeature:composum_composum-console:${project.version}”
>
> The only fixed part is the component / package name. These models come
> from a provisioning file but should work the same with packages.
>
> Anyhow I cannot use placeholders like '${project.groupId}' as the tool is
> not resolving them and hence fails when checking this as Maven Id.
>
> In addition when using the actual package name the ‘classifier’ is only
> used for the run modes.
>
> I tried to use the ‘-m’ option together with all packages in one call and
> it still does place all packages into their own model file.
>
> Cheers - Andy
