Re: Dependency on deprecated classes

2011-01-19 Thread Ivanhoe Abrahams
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.ari

Re: Dependency on deprecated classes

2011-01-19 Thread Valentin Mahrwald
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

Re: Dependency on deprecated classes

2011-01-19 Thread Alasdair Nottingham
Having deployed these bundles I get a different set of problems. These are fixed by deploying bundles with asm, slf4j and the jpa, JTA and config manager interface bundles. Also you shouldn't have org.apache.aries.application-0.3-SNAPSHOT and org.apache.aries.application.runtime-0.3-SNAPSHOT A

Re: Dependency on deprecated classes

2011-01-19 Thread Emily Jiang
Judging from the error messages, the bundles cannot be resolved because of the missing package of package=org.osgi.service.framework)(version>=1.0.0)(!(version>=2.0.0)). I had a quick look at the bundle lists. The bundle org.apache.aries.util-0.3-SNAPSHOT and org.apache.aries.blueprint-0.3-SNA