Imported package not resolved in Bundle | Community
Skip to main content
January 29, 2021
Solved

Imported package not resolved in Bundle

  • January 29, 2021
  • 2 replies
  • 4448 views

 There are few bundles are not resolved after deploy to local server 

com.bea.xml.stream -- Cannot be resolved
com.ctc.wstx.stax -- Cannot be resolved

com.google.crypto.tink.subtle -- Cannot be resolved
com.ibm.xml.xlxp.api.stax -- Cannot be resolved and overwritten by Boot Delegation
com.jcraft.jzlib -- Cannot be resolved
com.microsoft.applicationinsights.agent.internal.sdk -- Cannot be resolved
com.microsoft.applicationinsights.core.dependencies.codehaus.jettison -- Cannot be resolved
com.microsoft.applicationinsights.core.dependencies.codehaus.jettison.mapped -- Cannot be resolved
com.microsoft.applicationinsights.core.dependencies.google.protobuf.nano -- Cannot be resolved
com.ning.compress -- Cannot be resolved
com.ning.compress.lzf -- Cannot be resolved
com.ning.compress.lzf.util -- Cannot be resolved
com.opensymphony.xwork2 -- Cannot be resolved
com.opensymphony.xwork2.interceptor -- Cannot be resolved

javax.interceptor -- Cannot be resolved

lzma.sdk -- Cannot be resolved
lzma.sdk.lzma -- Cannot be resolved
net.jpountz.lz4 -- Cannot be resolved
net.jpountz.xxhash -- Cannot be resolved

net.sf.cglib.proxy -- Cannot be resolved
nu.xom -- Cannot be resolved
org.apache.avalon.framework.logger -- Cannot be resolved
org.apache.log -- Cannot be resolved
org.apache.logging.log4j -- Cannot be resolved
org.apache.logging.log4j.message -- Cannot be resolved
org.apache.logging.log4j.spi -- Cannot be resolved
org.conscrypt -- Cannot be resolved
org.dom4j -- Cannot be resolved
org.dom4j.io -- Cannot be resolved
org.dom4j.tree -- Cannot be resolved
org.eclipse.jetty.alpn -- Cannot be resolved
org.eclipse.jetty.npn -- Cannot be resolved
org.glowroot.instrumentation.api -- Cannot be resolved
org.jboss.marshalling -- Cannot be resolved
org.jboss.vfs -- Cannot be resolved
org.jdom -- Cannot be resolved
org.jdom.input -- Cannot be resolved
org.jdom2 -- Cannot be resolved
org.jdom2.input -- Cannot be resolved
org.kxml2.io -- Cannot be resolved

org.springframework.boot.autoconfigure.condition -- Cannot be resolved
org.springframework.boot.context.embedded -- Cannot be resolved
org.springframework.boot.web.servlet -- Cannot be resolved
org.springframework.context.annotation -- Cannot be resolved
org.springframework.web.method -- Cannot be resolved
org.springframework.web.servlet -- Cannot be resolved
org.springframework.web.servlet.config.annotation -- Cannot be resolved
org.springframework.web.servlet.handler -- Cannot be resolved

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Bhuwan_B

Update unsatisfied dependencies in red color with supported version maven dependencies in pom.xml

Reference : https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/cannot-resolve-imported-package-in-servlet-bundle/qaq-p/203029

 

2 replies

Bhuwan_B
Community Advisor
Bhuwan_BCommunity AdvisorAccepted solution
Community Advisor
January 29, 2021

Update unsatisfied dependencies in red color with supported version maven dependencies in pom.xml

Reference : https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/cannot-resolve-imported-package-in-servlet-bundle/qaq-p/203029

 

Kiran_Vedantam
Community Advisor
Community Advisor
January 29, 2021

Hi @archana_va_007,

 

As per the below error, you can do three things:

  1. Check the bundles that are not resolved in your local server. If the version is old, update the dependencies in your pom.xml to the latest
  2. If the bundles are missing, you can install them manually by downloading them. Just search like this: bundle name + download
    1. Ex: org.conscrypt bundle download
  3. If you want them to be installed via your code, you need to mention that explicitly in your ui.apps pom.xml in the embedded section. This will install the bundle every time on the build.

 

Hope this helps.

 

Thanks,

Kiran Vedantam.

January 29, 2021
@kiran_vedantam After adding <embeded> in core pom.xml also its not resolved. Any idea ..?