Failure to find com.adobe.fmdita:api:jar:3.5 | Community
Skip to main content
djohn98390536
djohn98390536
Level 4
July 19, 2024
Solved

Failure to find com.adobe.fmdita:api:jar:3.5

  • July 19, 2024
  • 3 replies
  • 1528 views

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)

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 DivrajSingh

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

3 replies

Vijendra1
Adobe Employee
Vijendra1Adobe Employee
Adobe Employee
July 19, 2024

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/introduction#configure-and-use-the-service-api-jar-from-public-maven-repository

 

    djohn98390536
    djohn98390536Author
    Level 4
    July 19, 2024

    thanks @vijendra1 for ur time to reply. 

      T
      Adobe Employee
      tasunil1Adobe Employee
      Adobe Employee
      July 19, 2024
      Hi,

      For Adobe public releases, we started posting from version Guides 4.0 onwards. You are looking for an older api.jar that is not available through Maven.

      To obtain it, you'll need to unzip the installer and navigate to <unzipdir>/jcr_root/libs/fmdita/osgi-bundles/install/api-3.5.jar. Copy this jar file and install it in your local Maven repository using the steps

      Then, you can use it.
       
      Regards
      Tarini
        djohn98390536
        djohn98390536Author
        Level 4
        July 19, 2024

        thanks @tasunil1  for ur time to reply. 

          DivrajSingh
          Adobe Employee
          DivrajSinghAdobe Employee
          Adobe Employee
          July 19, 2024

          @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/introduction 

            djohn98390536
            djohn98390536Author
            Level 4
            July 19, 2024

            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]

              DivrajSingh
              Adobe Employee
              DivrajSinghAdobe EmployeeAccepted solution
              Adobe Employee
              July 19, 2024

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

                Terms & ConditionsAccessibility statement

                Loading footer...