"org.apache.sling.api.request,version=[2.7,3) -- Cannot be resolved" in bundle.. | Community
Skip to main content
J
Jedy12
Level 2
July 10, 2024
Solved

"org.apache.sling.api.request,version=[2.7,3) -- Cannot be resolved" in bundle..

  • July 10, 2024
  • 3 replies
  • 1964 views

I faced this issue 

"org.apache.sling.api.request,version=[2.7,3) -- Cannot be resolved"

And I found the resolution like below link,

https://www.linkedin.com/pulse/aem-bundles-resolving-archetype-archetypeversion35-cannot-vikraman/

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-blogs/resolution-org-apache-sling-api-request-version-2-6-3-cannot-be/ba-p/462857

 

 

But, The version of installed Products is like this 6.5.20.0,

 

not like 

 

Please let me know how to solve this.

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 joerghoh

@estebanbustamante Updating to a newer SDK in your pom is only required when you want to use newer features and APIS of AEM CS. If you don't need that it should compiling with an older version of the SDK should work as well (although I recommend to upgrade the SDK version in the pom.xml regularly).

3 replies

aanchal-sikka
Community Advisor
aanchal-sikkaCommunity Advisor
Community Advisor
July 10, 2024

@jedy12 

 

It is a dependency issue. 

First, AEM 6.5 is different from aem-sdk. aem-sdk is for local development for AEM as a CLoud Service.

So, we cannot compare AEM 6.5 which uses service packs with AEM Cloud SDK.

 

The practice-core bundle seems to be a custom application. We would need to update the dependency of uber-jar to be equivalent with the AEM 6.5 + Service pack version.

Aanchal Sikka
    h_kataria
    Community Advisor
    h_katariaCommunity Advisor
    Community Advisor
    July 10, 2024

    This seems to be a practice project that you have created and it seems you might be trying to deploy a bundle meant for AEMaaCS on AEM 6.5.20.
    If you have created the project newly then make sure you have used the right arguments while creating it from the AEM archetpye specifically the aemVersion parameter. It should be 6.5.8 if it is not meant for cloud service. More details : https://github.com/adobe/aem-project-archetype 

      EstebanBustamante
      Community Advisor and Adobe Champion
      EstebanBustamanteCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      July 10, 2024

      Hi, 

      The dependency "org.apache.sling.api.request" is exported for either the uber-jar in AEMaaCS (AEM SDK) or an AEM service pack in the on-premise version. The solution depends on whether you are compiling an AEMaaCS project or working on the on-premise side: use a newer SDK version for AEMaaCS projects, or install a newer service pack for on-premise installations.

      You can find newer versions here:  https://experience.adobe.com/#/downloads/content/software-distribution/en/aemcloud.html


      Hope this helps

      Esteban Bustamante
        joerghoh
        Adobe Employee
        joerghohAdobe EmployeeAccepted solution
        Adobe Employee
        July 13, 2024

        @estebanbustamante Updating to a newer SDK in your pom is only required when you want to use newer features and APIS of AEM CS. If you don't need that it should compiling with an older version of the SDK should work as well (although I recommend to upgrade the SDK version in the pom.xml regularly).

          Terms & ConditionsAccessibility statement

          Loading footer...