Hi Andy, On Sat, 2020-06-06 at 16:40 -0700, Andreas Schaefer wrote: > You can use the -s option in the Sling Kickstart to prevent the > Kickstart to use the bundled Sling instance. That should just bring > up the Feature Model you provided there with -s. If you want to add > more Feature Models use as many -af as you need.
This is less about the bundled Sling instance (*), and more about having a generic mechanism for launching applications based on the feature model. I'm working on projects that use just the feature model, and not Sling. These would benefit from a more generic launcher. Thanks, Robert * - I think we should not bundle one at all, making the Kickstart more generic, but that's another discussion. > > Cheers - Andy > > > On Jun 5, 2020, at 2:07 PM, Robert Munteanu <[email protected]> > > wrote: > > > > Hi, > > > > For SLING-9499 [1] I am looking into launching a feature model > > application as part of a Maven build, for integration testing. > > > > I have looked into what the current Maven tooling offers and found: > > > > - slingfeature-maven-plugin:launch-features, that launches a single > > application, in-process, blocking, based on one or more feature > > files > > - sling-kickstart-maven-plugin:start, that launches one or more > > kickstart jars, out-of-process, non-blocking > > > > What I am looking for is something in the middle: launch a single > > application, based on feature files, out-of-process, non-blocking. > > I > > guess adding multiple applications won't be that hard. > > > > I think that we can enhance the Maven tooling to better support > > starting and stopping 'pure' feature model applications. This will > > be > > useful for people developing on top of the feature model but not > > with > > Sling. Then we can rebase the kickstart tooling to take advantage > > of > > the new enhancements. > > > > Thoughts? > > > > Thanks, > > Robert > > > > [1]: https://issues.apache.org/jira/browse/SLING-9499 > >
