And it hangs. It never reaches command level, and it never exits.
If I force a javax.servlet bundle into the situation, I start getting
similar complaints about the package that contains the DS annotations.
➜ rosapi1.5-master git:(dummy) ✗ assemblies/full-test/target/assembly/bin/karaf
2016-09-29 10:03:04,585 | ERROR | pool-6-thread-1 |
org.apache.karaf.features.internal.service.BootFeaturesInstaller |
org.apache.karaf.features.core - 4.0.6 | Error installing boot
features
org.osgi.service.resolver.ResolutionException: Unable to resolve root:
missing requirement [root] osgi.identity;
osgi.identity=rosapi-worker-flinx-sdk; type=karaf.feature; version=0;
filter:="(&(osgi.identity=rosapi-worker-flinx-sdk)(type=karaf.feature)(version>=0.0.0))"
[caused by: Unable to resolve rosapi-worker-flinx-sdk/1.5.0.SNAPSHOT:
missing requirement [rosapi-worker-flinx-sdk/1.5.0.SNAPSHOT]
osgi.identity; osgi.identity=rosapi-common; type=karaf.feature [caused
by: Unable to resolve rosapi-common/1.5.0.SNAPSHOT: missing
requirement [rosapi-common/1.5.0.SNAPSHOT] osgi.identity;
osgi.identity=io.dropwizard.metrics.servlets; type=osgi.bundle;
version="[3.1.2,3.1.2]"; resolution:=mandatory [caused by: Unable to
resolve io.dropwizard.metrics.servlets/3.1.2: missing requirement
[io.dropwizard.metrics.servlets/3.1.2] osgi.wiring.package;
filter:="(&(osgi.wiring.package=javax.servlet)(version>=2.5.0)(!(version>=4.0.0)))"]]]
at
org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42)[6:org.apache.karaf.features.core:4.0.6]
at
org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:235)[6:org.apache.karaf.features.core:4.0.6]
at
org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:158)[6:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:216)[6:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:263)[6:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:259)[6:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1176)[6:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1074)[6:org.apache.karaf.features.core:4.0.6]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_60]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_60]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_60]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_60]
On Thu, Sep 29, 2016 at 9:56 AM, Guillaume Nodet <[email protected]> wrote:
> Would you mind pasting the stack trace of the error you have please ?
>
>
> 2016-09-29 15:54 GMT+02:00 Benson Margulies <[email protected]>:
>>
>> 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é <[email protected]>
>> 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é
>> > [email protected]
>> > http://blog.nanthrax.net
>> > Talend - http://www.talend.com
>
>
>
>
> --
> ------------------------
> Guillaume Nodet
> ------------------------
> Red Hat, Open Source Integration
>
> Email: [email protected]
> Web: http://fusesource.com
> Blog: http://gnodet.blogspot.com/
>
