com.day.cq.wcm.tags,version=[6.1,7) -- Cannot be resolved | Community
Skip to main content
ashishkhadpe
New Participant
April 5, 2019
Solved

com.day.cq.wcm.tags,version=[6.1,7) -- Cannot be resolved

  • April 5, 2019
  • 6 replies
  • 3593 views

HI All,

I am upgrading from AEM 6.2 to AEM 6.4, I see that some packages can't be resolved. The description from the console is :

com.day.cq.wcm.tags,version=[6.1,7) -- Cannot be resolved

org.apache.sling.jcr.resource,version=[2.4,3) -- Cannot be resolved

I have also uber jar entry in my pom file as below :

<dependency>

   <groupId>com.adobe.aem</groupId>

   <artifactId>uber-jar</artifactId>

   <version>6.4.0</version>

   <classifier>apis</classifier>

   <scope>provided</scope>

</dependency>

Still getting above issue. Any suggestion on how it can 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 joerghoh

On my local AEM 6.4 SP3, the bundle "com.day.cq.wcm.cq-wcm-taglib" exports the java package "com.day.cq.wcm.tags" in version 7.1.0.
And "org.apache.sling.jcr.resource" is not exported at all. What kind of classes do you want to import from there?

For me it seems that you haven't updated the POM properly, and that you are still trying to deploy an AEM 6.2 application into an AEM 6.4.

6 replies

joerghoh
joerghohAccepted solution
Employee
April 9, 2019

On my local AEM 6.4 SP3, the bundle "com.day.cq.wcm.cq-wcm-taglib" exports the java package "com.day.cq.wcm.tags" in version 7.1.0.
And "org.apache.sling.jcr.resource" is not exported at all. What kind of classes do you want to import from there?

For me it seems that you haven't updated the POM properly, and that you are still trying to deploy an AEM 6.2 application into an AEM 6.4.

Prince_Shivhare
New Participant
April 8, 2019
ashishkhadpe
New Participant
April 8, 2019

Hi Jorg,

Yes I have recompiled my application and deployed back again. No specific version mentioned as well in POM.

Do we have any deprecation in terms of above packages?

joerghoh
Employee
April 6, 2019

Have you recompiled your application and deployed it then to AEM? Have you statements in your pom which pin this import to a specific version (basically overriding the data provided by the uber jar)?

Prince_Shivhare
New Participant
April 6, 2019

Could you please check in dpfinder and check the version required?

smacdonald2008
New Participant
April 5, 2019

Your POM dependencies are not correct.

LOok at this article where we successfully use Tag Manager API in a 6.4 project -- Adobe Experience Manager Help | Developing HTL Components that search for Adobe Experience Manager 6.4 Content Tags