Build Failure in 'All'

[sanchay1]

Error: Failed to execute goal com.adobe.aem:aemanalyser-maven-plugin:1.5.8:project-analyse (aem-analyser) on project wwg.all

I have updated the version of "aemanalyser" as mentioned here: https://stackoverflow.com/questions/71043425/failed-to-execute-build-analyzer-maven-plugin-in-local-...

But still the above error is comming.

Also, I'm using the latest AEM SDK version: AEM SDK for AEM v2023.7.12585.20230706T160730Z-230601

Any solution for this error?

[ManviSharma]

Hi,

The error message you provided suggests that there is an issue with the execution of the AEM Analyser Maven Plugin (com.adobe.aem:aemanalyser-maven-plugin) on your project wwg.all. Even though you have updated the version of the plugin as mentioned in the Stack Overflow post, the error persists. You also mentioned that you are using the latest AEM SDK version: AEM SDK for AEM v2023.7.12585.20230706T160730Z-230601.

I recommend the following step:

1. Verify the plugin configuration: Double-check your Maven configuration to ensure that the AEM Analyser Maven Plugin is correctly configured in your project's pom.xml file.

[BrianKasingli]

After taking a look at the repo.maven.apache.org for the Adobe Experience Manager SDK dependency, it looks like the version you are trying to build your AEM with does not exist, Maven Repository: com.adobe.aem » aem-sdk-api (mvnrepository.com).

You can try to change the version of your dependency that actually exists, and then rebuild the code. Try this version, 2023.7.12549.20230704T084019Z-230601.

[DPrakashRaj]

It seems the aem ask api that you are using on your Pom. Xml doesn’t exist.

latest aem sdk that I can see on maven repo is https://mvnrepository.com/artifact/com.adobe.aem/aem-sdk-api/2023.7.12549.20230704T084019Z-230601

try using this one 

[Nupur_Jain · Accepted solution]

Hi @sanchay1

looking at the error you are getting in build, the build is unable to find SDK in maven central repository. You need to setup adobe repository in order to download this particular artifact. For this, follow https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-17454.html?lang=en

Once, you make sure that the changes are made to setting.xml, you can start building the project again with mvn command with -U option after mvn.

-U option tell maven to update your local repository's remote dependencies (usually third party dependencies).

Hope it helps!

Thanks

Nupur

[Nikhil-Kumar]

It should be because you are not downloading the dependency from the correct URL. Try updating you pom.xml and settings.xml inside .m2 folder.