Build Failure - Project Analyser ......... FAILURE [ 7.763 s]

[NageshRaja]

Hi All,

I am getting a weird build issue - 

[ERROR] Error while reading API info from com.adobe.aem:aem-sdk-api:2025.9.22450.20250911T131210Z-250800

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal com.adobe.aem:aemanalyser-maven-plugin:1.6.4:analyse (default-analyse) on project projectA.all.analyse: Provider types not found in com.adobe.aem:aem-sdk-api:2025.9.22450.20250911T131210Z-250800. Please update to a more recent version of the API. -> [Help 1]

Now the weird thing is nowhere in my pom.xml is the 2025.9 version defined.
In my pom.xml the properties are defined as below - 

<aem.sdk.api>2024.7.17258.20240726T172406Z-240700</aem.sdk.api>

<dependency>
    <groupId>com.adobe.aem</groupId>
    <artifactId>aem-sdk-api</artifactId>
    <version>${aem.sdk.api}</version>
    <scope>provided</scope>
</dependency>

So couple of questions here if the pom.xml defines the version as 2024.7 then where does 2025.9 come up from? 
And how to get rid of this issue?

Thanks,

Nagesh

[SantoshSai]

Hi @NageshRaja,

1. The aemanalyser-maven-plugin resolves against the latest available SDK API unless pinned. If you’re using the default plugin configuration, Maven may be pulling the newest version from Adobe’s repo, not the one in your property.

2. Another dependency (e.g., uber-jar, project BOM, or parent archetype) could be dragging in the newer SDK API.

3. Sometimes Maven will cache and prefer a newer snapshot/release from Adobe’s Nexus repo if available. That explains why you see a 2025.9 build even though you didn’t specify it.

• Clean up your repo in case the wrong one is cached:

  mvn clean install -U

  or manually remove the ~/.m2/repository/com/adobe/aem/aem-sdk-api/2025.9* folder.

• Double-check your parent pom (all, ui.apps, core, etc.) for an <aem.sdk.api> override. Sometimes the archetype scaffolds multiple versions across modules.

[NageshRaja]

@SantoshSai thank you for the response but this didn't work - I tried -U but that just rebuilt the repo and the error again

Here's my pom.xml setting - 

<aemanalyser.version>1.6.4</aemanalyser.version>
<aem.sdk.api>2024.7.17258.20240726T172406Z-240700</aem.sdk.api>

<dependency>
    <groupId>com.adobe.aem</groupId>
    <artifactId>aem-sdk-api</artifactId>
    <version>${aem.sdk.api}</version>
    <scope>provided</scope>
</dependency>

<!-- AEM Analyser Plugin -->
<plugin>
    <groupId>com.adobe.aem</groupId>
    <artifactId>aemanalyser-maven-plugin</artifactId>
    <version>${aemanalyser.version}</version>
    <extensions>true</extensions>
</plugin>

[arunpatidar]

Hi @NageshRaja 

You can set exact version using below -

• sdkVersion : This property can be used to exactly specify the SDK version to be used for the analysis. If not set, the plugin will use the latest available SDK. The value for this property can also be specified via the command line by setting sdkVersion.

More info 

https://github.com/adobe/aemanalyser-maven-plugin/blob/main/aemanalyser-maven-plugin/README.md 

[NageshRaja]

hey @arunpatidar, 

this is the setting in my pom.xml where both versions are set yet the build picks up the latest

<aemanalyser.version>1.6.4</aemanalyser.version>
<aem.sdk.api>2024.7.17258.20240726T172406Z-240700</aem.sdk.api>

<!-- AEM Analyser Plugin -->
<plugin>
    <groupId>com.adobe.aem</groupId>
    <artifactId>aemanalyser-maven-plugin</artifactId>
    <version>${aemanalyser.version}</version>
    <extensions>true</extensions>
</plugin>
<dependency>
    <groupId>com.adobe.aem</groupId>
    <artifactId>aem-sdk-api</artifactId>
    <version>${aem.sdk.api}</version>
    <scope>provided</scope>
</dependency>