Hi Robert,

It looks like you need to define a larger start level for your bundle.  The
features declared in the starter have various "start-order" values from 1
to 20.

For example, something like this should work:

diff --git a/launcher/src/main/features/launcher.json
b/launcher/src/main/features/launcher.json
index 8e81e84..f846e20 100644
--- a/launcher/src/main/features/launcher.json
+++ b/launcher/src/main/features/launcher.json
@@ -1,6 +1,9 @@
 {

 
"id":"${project.groupId}:${project.artifactId}:slingosgifeature:launcher:${project.version}",
   "bundles": [
-    "com.example/core/1.0.0-SNAPSHOT"
+        {
+            "id":"com.example/core/1.0.0-SNAPSHOT",
+            "start-order":"20"
+        }
   ]
-}
\ No newline at end of file
+}


On Fri, Jul 9, 2021 at 7:22 AM Robert Munteanu <[email protected]> wrote:

> Hi,
>
> I'm prototyping a launcher module for the sling-project-archetype and
> I'm trying to do the following:
>
> - define a separate feature file (launcher.json) which includes a
> single bundle (core)
> - create an aggregate (app) which includes the launcher.json local
> aggregate + 2 features from the sling starter: nosample_base and
> oak_persistence_sns
> - analyse the app aggregate only
>
> However, it seems that the running the analysers errors out, with the
> core bundle listed as having unsatisfied dependencies, e.g.
>
> [ERROR] com.example:core:1.0.0-SNAPSHOT:  is importing package(s)
> [org.slf4j, javax.servlet, org.apache.sling.api.servlets,
> org.apache.sling.api, org.apache.sling.api.resource,
> org.apache.sling.models.annotations.injectorspecific,
> org.apache.sling.models.annotations, javax.jcr] in start level 0 but no
> bundle is exporting these for that start level.
>
> I've pushed the project to GH at
> https://github.com/rombert/sling-project-launcher-module , just run mvn
> clean install to see the error.
>
> What am I missing here? I think I should be able to assemble an
> application from external feature files and have the analyser run over
> all of them.
>
> Also, how can I exclude the validations comming from external
> (includeArtifact) features? They don't really matter to me I think ...
>
> Thanks,
> Robert
>
>
>
>

Reply via email to