That resolver failure seems to suggest that org.apache.aries.proxy-0.3-incubating-SNAPSHOT (although it is not clear which bundle 17.0 refers to) has a dependency on org.osgi.service.framework, which it does not seem to happen in my current workspace build. Does that rime with what you can see in the console?
Regards, Valentin On 19 Jan 2011, at 18:12, Ivanhoe Abrahams wrote: > Hi Mark > > Please can you explain the workaround a bit more? > > I have the following bundles deployed in a clean Felix 3.0.7 deploy (along > with some other bundles) > > org.apache.aries.util-0.3-SNAPSHOT > org.apache.aries.quiesce.api-0.3-SNAPSHOT > org.apache.aries.proxy-0.3-incubating-SNAPSHOT > org.apache.aries.jpa.container-0.3-SNAPSHOT > org.apache.aries.jpa.container.context-0.3-SNAPSHOT > org.apache.aries.jpa.blueprint.aries-0.3-SNAPSHOT > org.apache.aries.jpa.api-0.3-SNAPSHOT > org.apache.aries.blueprint-0.3-SNAPSHOT > org.apache.aries.application-0.3-SNAPSHOT > org.apache.aries.application.runtime-0.3-SNAPSHOT > org.apache.aries.application.api-0.3-SNAPSHOT > > However in startup immediately get following error message > > ERROR: Error starting > file:/C:/work/Felix-307/felix-framework-3.0.7/bundle/org.apache.aries.application-0.3-SNAPSHOT.jar > (org.osgi.framework.BundleException: Unresolved constraint in bundle > org.apache.aries.application [9]: Unable to resolv > e 9.0: missing requirement [9.0] package; > (&(package=org.apache.aries.blueprint)(version>=0.3.0)(!(version>=1.0.0))) [ca > used by: Unable to resolve 12.0: missing requirement [12.0] package; > (&(package=org.apache.aries.proxy)(version>=0.3.0)( > !(version>=1.0.0))) [caused by: Unable to resolve 17.0: missing requirement > [17.0] package; (&(package=org.osgi.service. > framework)(version>=1.0.0)(!(version>=2.0.0)))]]) > org.osgi.framework.BundleException: Unresolved constraint in bundle > org.apache.aries.application [9]: Unable to resolve > 9.0: missing requirement [9.0] package; > (&(package=org.apache.aries.blueprint)(version>=0.3.0)(!(version>=1.0.0))) > [caus > ed by: Unable to resolve 12.0: missing requirement [12.0] package; > (&(package=org.apache.aries.proxy)(version>=0.3.0)(!( > version>=1.0.0))) [caused by: Unable to resolve 17.0: missing requirement > [17.0] package; (&(package=org.osgi.service.fr > amework)(version>=1.0.0)(!(version>=2.0.0)))]] > at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3409) > at org.apache.felix.framework.Felix.startBundle(Felix.java:1719) > at > org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1148) > at > org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264) > at java.lang.Thread.run(Thread.java:619) > ERROR: Error starting > file:/C:/work/Felix-307/felix-framework-3.0.7/bundle/org.apache.aries.application.runtime-0.3-SNAP > SHOT.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle > org.apache.aries.application.runtime [11]: > Unable to resolve 11.0: missing requirement [11.0] package; > (&(package=org.osgi.service.blueprint)(version>=1.0.0)(!(ve > rsion>=2.0.0))) [caused by: Unable to resolve 12.0: missing requirement > [12.0] package; (&(package=org.apache.aries.prox > y)(version>=0.3.0)(!(version>=1.0.0))) [caused by: Unable to resolve 17.0: > missing requirement [17.0] package; (&(packag > e=org.osgi.service.framework)(version>=1.0.0)(!(version>=2.0.0)))]]) > org.osgi.framework.BundleException: Unresolved constraint in bundle > org.apache.aries.application.runtime [11]: Unable to > resolve 11.0: missing requirement [11.0] package; > (&(package=org.osgi.service.blueprint)(version>=1.0.0)(!(version>=2.0 > .0))) [caused by: Unable to resolve 12.0: missing requirement [12.0] package; > (&(package=org.apache.aries.proxy)(version > >=0.3.0)(!(version>=1.0.0))) [caused by: Unable to resolve 17.0: missing > >requirement [17.0] package; (&(package=org.osgi > .service.framework)(version>=1.0.0)(!(version>=2.0.0)))]] > > if I deploy equinox osgi-3.5.0.v20090520.jar as well, the startup process > proceeds much further until it gets other errors unrelated to aries. > > So as you can see I have included "org.apache.aries.application.runtime" > bundle but to no avail. > Do you mean that I need check out trunk and change something in one of the > pom.xml files and then build? > > I would really like to try the latest version of aries on Felix. > > Thanks in advance > Regards > Ivanhoe > > > > > On Sun, Jan 16, 2011 at 8:17 PM, Mark Nuttall <[email protected]> wrote: > Hello Ivanhoe, > The org.osgi.service.framework API is still under development within > the OSGi Alliance. It's subject to ongoing change, which is what > 'deprecated' means in this case. Felix has not yet implemented this > API or a functional equivalent. The 'workaround' for Felix is to > substitute org.apache.aries.application.runtime.isolated for > org.apache.aries.application.runtime. This bundle offers a simple > Aries application runtime which works, although providing no isolation > between different applications' bundles. > > Regards, > Mark > > On 16 January 2011 17:25, Ivanhoe Abrahams <[email protected]> wrote: > > Hi > > I just tried to install apache aries on Karaf, and I noticed a dependency on > > "org.osgi.service.framework" which seems to be only implemented by equinox. > > I was just wondering if there is a workaround so that I can install it on > > Felix as well. > > Thanks > > Ivanhoe > > BTW. It would be really great if someone has a ready made karaf feature file > > for apache aries. > > >
