Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Unable to build AEM maven project because failed to resolve cndNames

smrithig4775845
Level 2
Level 2

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?

AEM6.4 cndNames maven oak
1 Accepted Solution
SundeepKatepally
Correct answer by
Level 5
Level 5

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 .

 

View solution in original post

5 Replies
SundeepKatepally
Correct answer by
Level 5
Level 5

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 .

 

View solution in original post

smrithig4775845
Level 2
Level 2
we are not using the latest maven archetype, as the project was created few years back . 😞
BrianKasingli
Community Advisor
Community Advisor

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.

smrithig4775845
Level 2
Level 2
Hi BrianKasingil, I had tried the same thing, it downloaded the version 1.5.1 again but again the oakpal scanning was failing.