Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

I'm getting this error while building for AEMaaCS

Avatar

Level 4

[INFO] core-baemaacs ....................................... SUCCESS [ 0.800 s]
[INFO] core-baemaacs - Core ................................ SUCCESS [ 7.713 s]
[INFO] core-baemaacs - Repository Structure Package ........ SUCCESS [ 0.293 s]
[INFO] core-baemaacs - UI apps ............................. SUCCESS [ 1.166 s]
[INFO] core-baemaacs - UI content .......................... SUCCESS [ 0.084 s]
[INFO] core-baemaacs - UI config ........................... SUCCESS [ 0.094 s]
[INFO] core-baemaacs - All ................................. SUCCESS [ 20.141 s]
[INFO] core-baemaacs - Integration Tests ................... SUCCESS [ 14.737 s]
[INFO] core-baemaacs - Dispatcher .......................... FAILURE [ 0.011 s]
[INFO] core-baemaacs - UI Tests ............................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 46.935 s
[INFO] Finished at: 2023-04-24T12:42:29+05:30
[INFO] ------------------------------------------------------------------------
[WARNING] The requested profile "classic" could not be activated because it does not exist.
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.4:enforce (enforce-checksum-of-immutable-files) on project core-baemaacs.dispatcher.cloud: Unab
le to parse configuration of mojo org.apache.maven.plugins:maven-enforcer-plugin:1.4:enforce for parameter requireTextFileChecksum: Cannot create instance of interface org.ap
ache.maven.enforcer.rule.api.EnforcerRule: org.apache.maven.enforcer.rule.api.EnforcerRule

 

 

does anyone know that how to fix this issue?

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @vkarthick ,

Delete your maven repository under .m2/repository and then retry to build with below command:

mvn clean install -PautoInstallSinglePackage -Pclassic

If the above doesn't work then a workaround is that you skip the module which is causing build error by

mvn clean install -PautoInstallSinglePackage -Pclassic -Denforcer.skip=true

 
Hope it helps!

View solution in original post

4 Replies

Avatar

Employee Advisor

Hi @vkarthick ,

Have you created a new project , then which archetype are you using. Could you please post the command 

 

Thanks 

Bimmi Soi

 

 

Avatar

Level 4

"mvn -B archetype:generate -D archetypeGroupId=com.adobe.aem -D archetypeArtifactId=aem-project-archetype -D archetypeVersion=40 -D appTitle="core-baemaacs" -D appId="baem-library" -D groupId="cober.aem" -D aemVersion=cloud -DartifactId="core-baemaacs" -DfrontendModule=none -D includeExamples=n"

 

Avatar

Correct answer by
Community Advisor

Hi @vkarthick ,

Delete your maven repository under .m2/repository and then retry to build with below command:

mvn clean install -PautoInstallSinglePackage -Pclassic

If the above doesn't work then a workaround is that you skip the module which is causing build error by

mvn clean install -PautoInstallSinglePackage -Pclassic -Denforcer.skip=true

 
Hope it helps!

Avatar

Community Advisor

@vkarthick From the error we see clearly that while building the project it is taking "classic" profile which is not supported in AEMaaCS.

 

So make sure you delete it from the maven pom.xml file. And in first place i am not sure why 'classic' will be created as part of the latest archetypeVersion. 

You can creating a new repo from cloud manager that helps a lot.