Hi, In the Sling OAuth bundle I have a set up where I generate a standalone feature model based on
- Sling Starter 13-SNAPSHOT - the project's bundle - other dependencies not present in the Sling Starter see [1]. When building the project I need to attach the 'standalone' feature because otherwise it can't be resolved by the feature-launcher-maven- plugin [2]. This has the unfortunate side effect of installing/deploying the feature, which IMO does not make sense. I took a look at the codebases and the only thing that comes to mind is to update the feature-launcher-maven-plugin to look for the a feature file on disk, e.g. target/slingfeature-tmp/feature-app.json . That seems a bit risky though because the feature file location is not based on any kind of contract. Is there a better way of locating unattached feature files? I'm also happy for completely different ways of approaching the problem. Thanks, Robert [1]: https://github.com/apache/sling-org-apache-sling-auth-oauth-client/blob/cc6ad040631e0df8bb50f117fae7715b05a4d2b8/pom.xml#L71-L155 [2]: https://github.com/apache/sling-org-apache-sling-auth-oauth-client/blob/cc6ad040631e0df8bb50f117fae7715b05a4d2b8/pom.xml#L213-L219
