At the moment, I resolve these types of issues by setting felix.log.level=4
in etc/config.properties (or if you are using the latest snapshot Karaf
builds you can use use the new "dev:framework --enable-debug" command and
then restart).  This will give you more information about the fragment
resolution issues when resolution fails.

In this particular case, you are running into
https://issues.apache.org/jira/browse/FELIX-1919 which has had some
discussion recently and hopefully we can find a solution at some point.
 Richard's first comment on the issue contains the specifics on why this
happens.

Thanks,
Chris

--
Chris Custine
FUSESource :: http://fusesource.com
My Blog :: http://blog.organicelement.com
Apache ServiceMix :: http://servicemix.apache.org
Apache Felix :: http://felix.apache.org
Apache Directory Server :: http://directory.apache.org


On Sat, Jan 2, 2010 at 2:45 PM, jamie campbell <[email protected]> wrote:

> I'm setting a system up in karaf, with local shell enabled.  One of the
> bundles (maven info, groupId: org.hibernate ; artifactId:
> com.springsource.org.hibernate.annotations ; version 3.4.0.GA) gets to the
> "installed" state, but doesn't get to active or resolved.
>
> I've read the dependencies listed using
> http://www.springsource.com/repository/app/search , and verified they're
> satisfied.  I also went right to the pom and verified the dependencies
> listed there are satisfied.  I've also used the headers command in karaf,
> and verified that the import packages list is satisfied.  I read the mailing
> list archives for this list and googled, and had a brief bit of excitement
> thinking that "inspect package requirement" would be helpful, but it shows
> me nothing (literally bundle imports packages : nothing).
>
> Is there a shell command of some sort I can use on a bundle id to tell me
> "this bundle is still waiting for requirements satisfaction of blah, blah,
> and blah" ?
>
> -Jamie
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to