Bundle not startiing - Unresolved requirements | Community
Skip to main content
s1101v
Level 3
Mar 2, 2021 5:16 AM UTC
Solved

Bundle not startiing - Unresolved requirements

Hi All - I am getting the below error. Because of this issue, the bundle is not getting resolved. Can someone help with this?

 

03.02.2021 00:06:45.616 *ERROR* [ anonymous-nosite-127.0.0.1-777db039-8efb-4aec-80a5-04ac005ebd09 ] org.apache.felix.http.jetty %bundles.pluginTitle: Cannot start (org.osgi.framework.BundleException: Unable to resolve product-mgt-landing.core [658](R 658.1): missing requirement [product-mgt-landing.core [658](R 658.1)] osgi.wiring.package; (osgi.wiring.package=com.adobe.cq.wcm.core.components.internal.models.v1) Unresolved requirements: [[product-mgt-landing.core [658](R 658.1)] osgi.wiring.package; (osgi.wiring.package=com.adobe.cq.wcm.core.components.internal.models.v1)])
org.osgi.framework.BundleException: Unable to resolve product-mgt-landing.core [658](R 658.1): missing requirement [product-mgt-landing.core [658](R 658.1)] osgi.wiring.package; (osgi.wiring.package=com.adobe.cq.wcm.core.components.internal.models.v1) Unresolved requirements: [[product-mgt-landing.core [658](R 658.1)] osgi.wiring.package; (osgi.wiring.package=com.adobe.cq.wcm.core.components.internal.models.v1)]
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4368)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2281)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Kiran_Vedantam
Kiran_VedantamAccepted solution
New Participant
Mar 2, 2021 6:01 AM UTC

Check the core.wcm.components.version and update it to the latest.

 

Hope this helps.

 

Thanks,

Kiran Vedantam.

View reply

3 replies

joerghoh
joerghoh
Employee
Mar 7, 2021 6:02 PM UTC

That package is not exported by the bundle (just checked it with version 2.13.4). If you want to extend these core components, please check the documentaiton at https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/customizing.html?lang=en#customizing-the-logic-of-a-core-component

 

 

Translate
    user05162
    Employee
    Mar 2, 2021 2:20 PM UTC

    Karan is right, This issue is related to core components version. Check [1] for more details:

     

    [1] https://github.com/adobe/aem-core-wcm-components/releases

     

    Translate
      Kiran_Vedantam
      Kiran_VedantamAccepted solution
      New Participant
      Mar 2, 2021 6:01 AM UTC

      Check the core.wcm.components.version and update it to the latest.

       

      Hope this helps.

       

      Thanks,

      Kiran Vedantam.

      Translate
        Terms & ConditionsAccessibility statement

        Loading footer...