Hi David, On Tue, 2018-04-17 at 16:21 +0300, David Bosschaert wrote: > Hi Robert, > > This is using the OSGi Framework launch API to get the framework and > obtain > its resolver service. You should be able to get past it by adding the > Felix > Framework to the launch path.
I tried to do so, now launching with $ java -cp \ ../../../whiteboard/featuremodel/feature-applicationbuilder/target/org.apache.sling.feature.applicationbuilder-0.0.1-SNAPSHOT.jar:~/.m2/repository/org/apache/felix/org.apache.felix.framework/5.6.8/org.apache.felix.framework-5.6.8.jar \ org.apache.sling.feature.applicationbuilder.impl.Main \ -d features/ \ -u ~/.m2/repository \ -o sling.json And I get the same error. The felix jar file seems to be the right one $ jar tf ~/.m2/repository/org/apache/felix/org.apache.felix.framework/5.6.8/org.apache.felix.framework-5.6.8.jar | grep -e 'META-INF/.*FrameworkFactory' META-INF/services/org.osgi.framework.launch.FrameworkFactory Using '-XX:+TraceClassLoading' does not show any classes being loaded from the Felix jar. I feel like I'm missing something simple, but I have no idea what ... Any further ideas? Thanks, Robert
