Error in Import Packages com.adobe.aemfd.docmanager,version=[1.9,2) -- Cannot be resolved | Community
Skip to main content
S
StanleyLi2
Level 1
May 22, 2026
Solved

Error in Import Packages com.adobe.aemfd.docmanager,version=[1.9,2) -- Cannot be resolved

  • May 22, 2026
  • 2 replies
  • 42 views

 I am currently migrating AEM Classic Forms to AEM as a Cloud Service (AEMaaCS) and need to generate PDFs using an XDP template and XML data.

I attempted to use the Output Service API as described in the documentation:

Generate PDF documents using output service | Adobe Experience Manager

However, I am encountering import/package resolution errors when deploying my bundle to the local AEMaaCS SDK.

Current Dependency (not working in AEMaaCS)

<dependency>
<groupId>com.adobe.aemfd</groupId>
<artifactId>aemfd-client-sdk</artifactId>
<version>6.1.152</version>
</dependency>

From my investigation, this dependency is intended for AEM 6.x (on-prem/AMS) and is not compatible with AEM Forms on Cloud Service.

Proposed Approach

It seems that for AEM Forms CS, the correct dependency should be:

<!-- Source: https://mvnrepository.com/artifact/com.adobe.aem/aem-forms-sdk-api -->

<dependency>

<groupId>com.adobe.aem</groupId>

<artifactId>aem-forms-sdk-api</artifactId>

<version>2026.03.30.00-260300</version>

<scope>compile</scope>

</dependency>

``

Questions

  1. Could you please confirm if this is the correct dependency/version for compatibility with:

    aem-forms-addon-2026.03.30.00-260300

  2. How can I obtain this JAR/artifact?

    • Is it available via a public Maven repository, or
    • Does it require access through Adobe’s private repository / Software Distribution?

  3. Are there any additional configuration steps required to use the Output Service in AEM Forms CS (compared to AEM 6.x)?

Please let me know if I’m missing anything in the setup.

Thanks in advance for your help.

 

 

Best answer by Pranay_M

Hi ​@StanleyLi2,

 

Thanks for the detailed investigation. Your understanding is correct: the dependency `com.adobe.aemfd:aemfd-client-sdk` is intended for older AEM 6.x / on-prem / AMS usage and is **not** the right dependency model for **AEM Forms as a Cloud Service**.

For **AEM Forms as a Cloud Service**, the correct Java API artifact is:

<dependency>
    <groupId>com.adobe.aem</groupId>
    <artifactId>aem-forms-sdk-api</artifactId>
    <version>2026.03.30.00-260300</version>
    <scope>provided</scope>
</dependency>


Assuming your local/runtime environment is using **`aem-forms-addon-2026.03.30.00-260300`**, that version alignment is the right approach.

### A few important notes

- For AEMaaCS custom code running **inside AEM**, we recommend using the Forms OSGi APIs directly, for example `com.adobe.fd.output.api.OutputService`, rather than older remote client SDK patterns.
- In most AEM bundle projects, the dependency scope should be **`provided`** so the runtime supplies the API packages.
- The old AEM 6.5 / JEE quick starts and client-SDK patterns are not the right reference model for Forms CS.

### How to obtain the artifact

- The **`aem-forms-sdk-api`** artifact is intended to be consumed as the Forms CS SDK API dependency.
- The **AEM Forms add-on feature archive** (`aem-forms-addon-<version>.far`) for the local SDK is delivered separately through **Software Distribution**.

### Additional setup required for local AEMaaCS SDK

For local development and testing, please also verify the following:

1. The matching **AEM Forms add-on** is installed into your local AEM SDK instance.
2. The local **Forms native / docker-based SDK services** are started, since document-generation capabilities depend on that local setup.
3. Your custom code is compiled against the matching Forms CS SDK version.
4. If applicable, the invoking user/service account has the required Forms permissions such as membership in the relevant Forms user groups.

### Recommendation

If your target runtime is: aem-forms-addon-2026.03.30.00-260300

then using: com.adobe.aem:aem-forms-sdk-api:2026.03.30.00-260300

is the correct dependency choice.

If helpful, we can also share a small working example showing:
- the Maven dependency setup
- a sample OSGi service/servlet using `OutputService`
- and the local SDK prerequisites for successful deployment/testing

# Sources
- [Generate PDF documents using output service](https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/forms/forms-cs-output-and-forms-service/outputservice)
- [How do I set up a local development environment for AEM Forms?](https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/forms/setup-configure-migrate/setup-local-development-environment)

Thanks

2 replies

A
akhil_merupula
Level 4
May 22, 2026

Hi ​@StanleyLi2,
 

This is happening because the dependency you’re using (aemfd-client-sdk and com.adobe.aemfd.docmanager) is from AEM 6.x Forms (on-prem/AMS) and isn’t available in AEM as a Cloud Service. That’s why the package can’t be resolved in AEMaaCS.

In Cloud Service, Adobe has moved away from the old Java APIs for Forms. Instead, PDF generation is expected to be done via the Forms Output Service REST APIs, not through local SDK/JAR dependencies.

So in your case:

  • The current aemfd-client-sdk dependency won’t work in AEMaaCS
  • You should remove the docmanager usage entirely
  • And invoke the Output Service using REST (HTTP call with proper auth)

Regarding the dependency you suggested (aem-forms-sdk-api) that’s not something you’ll typically use for this scenario, and it’s not publicly available via Maven Central anyway.

For your questions:

  1. That dependency/version isn’t required for Output Service in AEM Forms CS
  2. There’s no public Maven artifact for this Adobe usually provides SDKs via Software Distribution, but for Output Service you don’t need it
  3. No additional OSGi setup is really needed just REST integration + authentication

So overall, the main change here is shifting from Java API-based integration → REST-based integration, which is the supported pattern in AEMaaCS.

    P
    Adobe Employee
    Pranay_MAdobe EmployeeAccepted solution
    Adobe Employee
    May 25, 2026

    Hi ​@StanleyLi2,

     

    Thanks for the detailed investigation. Your understanding is correct: the dependency `com.adobe.aemfd:aemfd-client-sdk` is intended for older AEM 6.x / on-prem / AMS usage and is **not** the right dependency model for **AEM Forms as a Cloud Service**.

    For **AEM Forms as a Cloud Service**, the correct Java API artifact is:

    <dependency>
        <groupId>com.adobe.aem</groupId>
        <artifactId>aem-forms-sdk-api</artifactId>
        <version>2026.03.30.00-260300</version>
        <scope>provided</scope>
    </dependency>


    Assuming your local/runtime environment is using **`aem-forms-addon-2026.03.30.00-260300`**, that version alignment is the right approach.

    ### A few important notes

    - For AEMaaCS custom code running **inside AEM**, we recommend using the Forms OSGi APIs directly, for example `com.adobe.fd.output.api.OutputService`, rather than older remote client SDK patterns.
    - In most AEM bundle projects, the dependency scope should be **`provided`** so the runtime supplies the API packages.
    - The old AEM 6.5 / JEE quick starts and client-SDK patterns are not the right reference model for Forms CS.

    ### How to obtain the artifact

    - The **`aem-forms-sdk-api`** artifact is intended to be consumed as the Forms CS SDK API dependency.
    - The **AEM Forms add-on feature archive** (`aem-forms-addon-<version>.far`) for the local SDK is delivered separately through **Software Distribution**.

    ### Additional setup required for local AEMaaCS SDK

    For local development and testing, please also verify the following:

    1. The matching **AEM Forms add-on** is installed into your local AEM SDK instance.
    2. The local **Forms native / docker-based SDK services** are started, since document-generation capabilities depend on that local setup.
    3. Your custom code is compiled against the matching Forms CS SDK version.
    4. If applicable, the invoking user/service account has the required Forms permissions such as membership in the relevant Forms user groups.

    ### Recommendation

    If your target runtime is: aem-forms-addon-2026.03.30.00-260300

    then using: com.adobe.aem:aem-forms-sdk-api:2026.03.30.00-260300

    is the correct dependency choice.

    If helpful, we can also share a small working example showing:
    - the Maven dependency setup
    - a sample OSGi service/servlet using `OutputService`
    - and the local SDK prerequisites for successful deployment/testing

    # Sources
    - [Generate PDF documents using output service](https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/forms/forms-cs-output-and-forms-service/outputservice)
    - [How do I set up a local development environment for AEM Forms?](https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/forms/setup-configure-migrate/setup-local-development-environment)

    Thanks

      Terms & ConditionsAccessibility statement

      Loading footer...