When adding a new dependency in the POM file of an OSGI bundle (which is deployed inside an AEM package to CRX) I will often see a number of unresolved dependencies in the OSGI console. The bundle will fail to activate.
org.jaxen.dom -- Cannot be resolved
org.jaxen.dom4j -- Cannot be resolved
org.jaxen.jdom -- Cannot be resolved
org.jaxen.pattern -- Cannot be resolved
org.jaxen.saxpath -- Cannot be resolved
org.jdom -- Cannot be resolved
org.jdom.input -- Cannot be resolved
org.jdom.output -- Cannot be resolved
How can I debug this type of problem? How can I understand why those dependencies are required yet cannot be resolved?
I can see in the POM that the bundle has been configured as follows:
All these dependencies should already present if not shipped with the bundle jar/package. you can check the stdout log to see the details on why these dependencies are not resolved. in case these dependencies are part of some other bundle package, please ensure the other bundle should get started first, you can control it via start-up level of the bundle.