Unable to build AEM maven project because failed to resolve cndNames | Community
Skip to main content
Level 3
August 20, 2020
Solved

Unable to build AEM maven project because failed to resolve cndNames

  • August 20, 2020
  • 3 replies
  • 2843 views

Hi Team,

 

I am unable to build a maven AEM project because of failure to resolve cndNames.

Failed to execute goal net.adamcin.oakpal:oakpal-maven-plugin:1.5.1:scan (default) on project *******: Failed to execute package scan. Failed to resolve cndNames.: Failed to find node type definition on classpath for cndName exportnodetype.jsp

 

Can someone please help me out here?

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 SundeepKatepally

Which maven archetype you are using ?

Latest version is 22 , i don't see any error with the latest archetype. 

 

Also in the maven archetype the mentioned plug in (net.adamcin.oakpal:oakpal-maven-plugin)  is not there .

 

3 replies

SundeepKatepally
Community Advisor
SundeepKatepallyCommunity AdvisorAccepted solution
Community Advisor
August 20, 2020

Which maven archetype you are using ?

Latest version is 22 , i don't see any error with the latest archetype. 

 

Also in the maven archetype the mentioned plug in (net.adamcin.oakpal:oakpal-maven-plugin)  is not there .

 

Level 3
August 21, 2020
we are not using the latest maven archetype, as the project was created few years back . 😞
BrianKasingli
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
August 20, 2020

It looks like the dependency has an error, try deleting the artifact in your ~/.m2 file, include this dependency in your root + core pom.xml, and try to re-download & rebuild your project.

<!-- https://mvnrepository.com/artifact/net.adamcin.oakpal/oakpal-maven-plugin --> <dependency> <groupId>net.adamcin.oakpal</groupId> <artifactId>oakpal-maven-plugin</artifactId> <version>1.5.1</version> </dependency>

I hope this works.

Level 3
August 21, 2020
Hi BrianKasingil, I had tried the same thing, it downloaded the version 1.5.1 again but again the oakpal scanning was failing.
arunpatidar
Community Advisor
Community Advisor
August 24, 2020