I think that because you must not reference camel-osgi in your Manifest but instead camel-* (core, blueprint, cdi,cxf,jms...)-2.12-0 because now their manifests are filled.
2014-02-03 Laci Gaspar <[email protected]>: > yes, you're right... but If I look here: > mvnrepository.com/artifact/org.apache.camel/camel-osgi > the latest version is 2.3.0 > confused... > > > On 03.02.2014 14:09, Charlie Mordant wrote: > > Hi, > > I think you're right in your interpretation! > > But, adding your dependency don't resolve the problem because 2.3.0 < > 2.12.0 > > Regards, Charlie > > > > 2014-02-03 Laci Gaspar <[email protected]>: > >> Hi >> I get the following error when I want to install bundle: >> Error executing command: Error installing bundles: >> Unable to start bundle >> mvn:ch.curabill.msp.service/templateRoute/1.0-SNAPSHOT: Unresolved >> constraint in bundle templateRoute [132]:Unable to resolve 132.0: missing >> requirement [132.0] >> osgi.wiring.package;(&(osgi.wiring.package=org.apache.camel.osgi)(version>=2.12.0)(!(version>=3.0.0))) >> >> First, how do I read such an error message? >> Am I right in my interpretation that org.apache.camel.osgi is missing >> with a 2.12.0 <= version < 3.0.0 ? >> >> I tried to add a dependency to my pom: >> <dependency> >> <groupId>org.apache.camel</groupId> >> <artifactId>camel-osgi</artifactId> >> <version>2.3.0</version> >> </dependency> >> >> but that didn't help. >> >> Any help is appreciated. >> Regards, >> Laci >> > > > -- Cordialement, Charlie Mordant
