I'm getting this error while building for AEMaaCS | Community
Skip to main content
K
KarthickVe
Level 4
April 24, 2023
Solved

I'm getting this error while building for AEMaaCS

  • April 24, 2023
  • 3 replies
  • 1634 views

[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?

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 TarunKumar

Hi @karthickve ,

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!

3 replies

B
Adobe Employee
BimmiSoAdobe Employee
Adobe Employee
April 24, 2023

Hi @karthickve ,

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

 

Thanks 

Bimmi Soi

 

 

    K
    KarthickVeAuthor
    Level 4
    April 24, 2023

    "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"

     

      TarunKumar
      Community Advisor
      TarunKumarCommunity AdvisorAccepted solution
      Community Advisor
      April 24, 2023

      Hi @karthickve ,

      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!

        Jagadeesh_Prakash
        Community Advisor
        Jagadeesh_PrakashCommunity Advisor
        Community Advisor
        April 24, 2023

        @karthickve 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. 

         

          Terms & ConditionsAccessibility statement

          Loading footer...