I am trying to use Baseline API and getting the below error can some body help to fix the issue.
Could not resolve dependencies for project org.example.core:jar:0.0.1-SNAPSHOT: Could not find artifact com.adobe.fmdita:api:jar:3.5 in adobe-public-releases (https://repo.adobe.com/nexus/content/groups/public)
Solved! Go to Solution.
Views
Replies
Total Likes
@djohn98390536 : if you are trying this on your local, you have to compile by adding following to the parent pom :
<configuration>
<failOnAnalyserErrors>false</failOnAnalyserErrors>
</configuration>
But if this is happening on cloud environment deployment (although its already handled on cloud for everyone) - you need to raise a support ticket and share that with us - it may require checking your cloud environment .
Did you try adding the dependency in your pom.xml?
Try this link -> https://experienceleague.adobe.com/en/docs/experience-manager-guides/using/api-reference/introductio...
thanks @Vijendra1 for ur time to reply.
@djohn98390536 : which version of AEM Guides are you using? Depending on that you have to use the corresponding version of api jar. And as @tasunil1 mentioned if you are on an older version the api jar is not available in public repo. However for recent versions what @Vijendra1 mentioned is applicable.
All of the methods are documented on this page - https://experienceleague.adobe.com/en/docs/experience-manager-guides/using/api-reference/introductio...
Hi @DivrajSingh i am using december version of Guides .
By Adding this now the issue got resolved .
<dependency>
<groupId>com.adobe.aem</groupId>
<artifactId>aem-guides-sdk-api</artifactId>
<version>2023.12.0</version>
</dependency>
But getting new error in all.pom file.
Failed to execute goal com.adobe.aem:aemanalyser-maven-plugin:1.4.10:project-analyse (aem-analyser) on project guides-practice.all: One or more feature analyser(s) detected feature error(s), please read the plugin log for more details -> [Help 1]
@djohn98390536 : if you are trying this on your local, you have to compile by adding following to the parent pom :
<configuration>
<failOnAnalyserErrors>false</failOnAnalyserErrors>
</configuration>
But if this is happening on cloud environment deployment (although its already handled on cloud for everyone) - you need to raise a support ticket and share that with us - it may require checking your cloud environment .
Thanks @DivrajSingh for ur time to reply .In local its working as expected now after adding the above config. In cloud if any issue happens i ll raise the ticket .
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies