How can I find unsatisfied constraints of a bundle which didn’t start from Apache Karaf console? I.e. what is its equivalent of Equinox’s diag command?
How can I find unsatisfied constraints of a bundle which didn’t start from Apache
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How can I find unsatisfied constraints of a bundle which didn’t start from Apache Karaf console? I.e. what is its equivalent of Equinox’s diag command?
Which version of Karaf are you using? The following should be relevant to Karaf 2.x
Annoyingly the package:imports/package:exports commands only work on a bundle in the STARTED state.
If the bundle is only INSTALLED you can use:
headers ${BUNDLE NUMBER}will highlight any missing imports in red.Also trying to start a bundle should print to the console any unresolved constraints as an LDAP filter expression.