API Dependency not resolved | Community
Skip to main content
Lokesh_Shivalingaiah
Lokesh_Shivalingaiah
Level 10
July 20, 2016

API Dependency not resolved

  • July 20, 2016
  • 3 replies
  • 12994 views

I have included a below dependency in my project ( AEM 6.1 )

<dependency> <groupId>com.adobe.cq.commerce</groupId> <artifactId>cq-commerce-core</artifactId> <version>5.13.12</version> <scope>provided</scope> </dependency>

I have checked in the depfinder and used the same version aswell.

When I deploy, bundle is in installed state with the below error

     
Imported Packagescom.adobe.cq.commerce.api,version=[1.2,2) -- Cannot be resolved

 

Anybody encountered the same and know what is the issue, do let me know 

 

Thanks!

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

    3 replies

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    July 20, 2016

    Hi Lokesh,

    I have asked internal Team with this query.

    I will revert you back soon.

    Thanks and Regards

    Kautuk Sahni

    Kautuk Sahni
    Lokesh_Shivalingaiah
    Lokesh_ShivalingaiahAuthor
    Level 10
    July 20, 2016

    Thanks Kautuk!

    Even in 6.2, I get the below error

         
    Imported Packagescom.adobe.cq.commerce.api,version=[3.4,4) -- Cannot be resolved
     

     

    with the dependency used as per the depfinder

    <dependency> <groupId>com.adobe.cq.commerce</groupId> <artifactId>cq-commerce-core</artifactId> <version>5.14.102</version> <scope>provided</scope> </dependency>

    R
    rahul_kumar11
    Level 3
    October 13, 2016

    samery56615784 wrote...

    Is this issue resolved? We are facing same issue in both 6.1 and 6.2 as well?

     

    is this issue resolve, same issue i am also facing with 6.1. We have not added any dependency in any of the pom file for commerce, please help


    Hi,

    Is the issue resolved?

    Thanks,

    Kumar

    smacdonald2008
    smacdonald2008
    Level 10
    August 17, 2016

    To all facing this issue, join Ask the experts next tues. Lokesh is the presenter and will be covering this topic. Sign up here: http://scottsdigitalcommunity.blogspot.ca/2016/08/working-with-aem-ecommerce-august-2016.html. 

    joerghoh
    Adobe Employee
    joerghohAdobe Employee
    Adobe Employee
    October 13, 2016

    Hi,

    looks like that there has been some change in the Commerce API. Please check the version of the java package "com.adobe.cq.commerce.api", which is exported by the "cq-commerce-core" bundle. You can find this information in the bundle details of this bundle on the OSGI webconsole. It should be version 3.1.0.

    So it rather looks like your bundles which depend on this commerce API are built with the wrong dependency. They should have an import statement like "version=(3.4]" to make the import work. You might want to check the uber.jar for the correct export statment and maybe overwrite this export in maven.

    Jörg

    Terms & ConditionsAccessibility statement

    Loading footer...