Actually, you are using multi-stage: stage1 is (wrap) and stage2 is all
the rest.
I would recommend to group all dependency features in stage1 and the
rest in stage2.
Regards
JB
On 09/29/2016 03:54 PM, Benson Margulies wrote:
Hi JB,
I let the maven plugin write org.apache.karaf.features.cfg, so I don't
know, to be honest, if I'm using multi-stage.
_Without_ the failing prerequisites, I have the following content of
org.apache.karaf.features.cfg. I'm using the property editor feature
to turn off capability enforcement.
rosapi-all-sdks is just a bag of <feature> declarations for other
features. Things break when I try to make one of them a prerequisite
of another. My problem is really to prevent the activation of a few
bundles until another bundle is safely under control, and I am hoping
for a workaround in the interim until we can really fix this with DS
in a few weeks.
#Modified by org.apache.karaf.tools.utils.KarafPropertiesFile
#Thu Sep 29 09:49:19 EDT 2016
featuresBootAsynchronous=false
serviceRequirements=disable
featuresBoot = \
(wrap), \
log, \
rosapi-front-end-anvils-transport, \
bean-validation-support, \
rosapi-worker-common, \
ssh, \
rosapi-front-end-logstash-request-tracker, \
rosapi-front-end-service, \
aries-blueprint, \
feature, \
jaas, \
diagnostic, \
rosapi-worker-download-text-extraction-component, \
rosapi-front-end-null-request-tracker, \
bundle, \
rosapi-all-sdks, \
rosapi-front-end-local-usage-tracker, \
package, \
scr, \
rosapi-common, \
cxf-jaxrs, \
rosette-api, \
rosapi-front-end-embedded-transport, \
system, \
shell, \
shell-compat, \
config
featuresRepositories = \
mvn:com.basistech.ws/rosapi-features/1.5.0-SNAPSHOT/xml/features, \
mvn:org.apache.karaf.features/standard/4.0.6/xml/features, \
mvn:org.apache.cxf.karaf/apache-cxf/3.1.4/xml/features, \
mvn:org.apache.karaf.features/framework/4.0.6/xml/features
On Thu, Sep 29, 2016 at 9:47 AM, Jean-Baptiste Onofré <j...@nanthrax.net> wrote:
Hi Benson,
do you use multi-stage in featuresBoot ?
Regards
JB
On 09/29/2016 03:33 PM, Benson Margulies wrote:
Folks,
I build an assembly in which all the feature are boot features,
because they are all going to be used.
When I try to make one of them a prerequisite of another, I get a
wiring error, because, apparently, the dependency tree at the package
level is not being respected in wiring the bundles.
All of this is a temporary stopgap until some components get correct
DS @Reference dependencies, which some of them lack.
Questions: Am I making an error using boot features? I realize that
this report lacks specificity. I could try to build up a model on
github.
TIA,
benson
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
