com.adobe.acs.commons.ondeploy,version=[1.1,2) -- Cannot be resolved - AEM as Cloud | Community
Skip to main content
S
Adobe Employee
Sandeep-LAdobe Employee
Adobe Employee
March 27, 2025
Solved

com.adobe.acs.commons.ondeploy,version=[1.1,2) -- Cannot be resolved - AEM as Cloud

  • March 27, 2025
  • 3 replies
  • 1117 views

Hello ALL!!

While Migrating AEM Assets from AEM6.5 to AEM as Cloud, facing the below issue...

 

Bundle is not getting resolved in /system/console/bundles
com.adobe.acs.commons.ondeploy,version=[1.1,2) -- Cannot be resolved
com.adobe.acs.commons.ondeploy.scripts,version=[1.1,2) -- Cannot be resolved

Current ACS version in main pom.xml:

<dependency>
        <groupId>com.adobe.acs</groupId>
        <artifactId>acs-aem-commons-bundle</artifactId>
        <version>4.5.0</version>
        <scope>provided</scope>
</dependency>

Updated the ACS dependency to 6.11.0, but still the same...

 

If anyone faced the same or related issue, please post your suggestions..

 

Appreciated if any quick responses!

Thanks!

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 Sandeep-L

@kautuk_sahni- After multiple discussions, the requirements were updated to exclude the 'on-deploy' scripts.
Consequently, these scripts were removed, leading to the bundle operating as expected!!

Thanks!

3 replies

Tethich
Community Advisor
TethichCommunity Advisor
Community Advisor
March 27, 2025

Hi @sandeep-l 

 

Not sure exactly what is happening specifically on your project, but it seams that third party (in your case the ACS Commons) dependency is not getting embedded upon deployment. Maybe this article can help you:
- https://myaemlearnings.blogspot.com/2021/08/embedding-third-party-dependencyosgi.html

 

But also please be aware of the followings:
- OnDeploy scripts are not compatible with AEMaaCS: https://adobe-consulting-services.github.io/acs-aem-commons/features/on-deploy-scripts/index.html . Because I see that is not resolving the com.adobe.acs.commons.ondeploy package.
- Check the compatibility matrix if it helps: https://adobe-consulting-services.github.io/acs-aem-commons/pages/compatibility.html

    S
    Adobe Employee
    Sandeep-LAdobe EmployeeAuthor
    Adobe Employee
    March 28, 2025

    Hey @tethich,
    Yes, It is not compatible with AEM as CS.
    Will need to look for alternative approach to proceed further.


    Thanks for the Response!!

     

      AmitVishwakarma
      Community Advisor
      AmitVishwakarmaCommunity Advisor
      Community Advisor
      March 27, 2025

      Hi @sandeep-l ,

      1. Check ACS Commons Version

      You mentioned updating to ACS Commons 6.11.0, which is correct for AEMaaCS. However, confirm that your entire project is aligned with supported versions.

      Check the compatibility matrix here:
      ACS Commons Compatibility

      2. Verify On-Deploy Scripts Compatibility

      On-Deploy scripts are not supported in AEM as a Cloud Service. You should remove any dependencies related to com.adobe.acs.commons.ondeploy from your project.

      Refer to this official ACS Commons page:

      3. Ensure Proper Dependency Inclusion

      Modify your pom.xml to include ACS Commons properly:

      <dependency> <groupId>com.adobe.acs</groupId> <artifactId>acs-aem-commons-bundle</artifactId> <version>6.11.0</version> <scope>provided</scope> </dependency>

      Ensure there are no old versions of ACS Commons still referenced in other modules.

      4. Check Embedding in the Core Bundle

      If the ACS Commons package is still not resolving, explicitly embed it in your core bundle:
      Modify core/pom.xml:

      <Embed-Dependency> com.adobe.acs:acs-aem-commons-bundle;scope=compile|runtime </Embed-Dependency>

      Run:mvn clean install -PautoInstallSinglePackage

      5. Verify Installation on AEM

      Go to AEM Web Console (/system/console/bundles) and check if ACS Commons is installed and active.

      If it appears as Installed but not Active, restart the bundle manually.

      6. Rebuild and Deploy

      Try a full rebuild: mvn clean install -DskipTests
      If deploying via Cloud Manager, ensure no package conflicts.

      Regards,
      Amit

        S
        Adobe Employee
        Sandeep-LAdobe EmployeeAuthor
        Adobe Employee
        March 28, 2025

        Hey @amitvishwakarma,

        On-Deploy scripts are used in my project, So need to look for best alternative approach.
        If any suggestions or ideas related to - Accepted!

        Thanks for the info!

          giuseppebaglio
          giuseppebaglio
          Level 10
          March 28, 2025

          For AEM as a Cloud Service, alternatives to ACS AEM Commons On-Deploy Scripts include:

          1. Repoinit Scripts: These scripts can be used to establish nodes under /var or other necessary paths. They are executed during the repository initialization phase and can be tailored to specific run modes. This approach is recommended for setting up initial content structures that do not require replication.

          2. Sling Pipes: Sling Pipes can be utilized for content processing and transformation tasks. They provide a flexible way to handle content updates and migrations, making them a suitable alternative.

          3. Managed Control Process (MCP): The ACS Commons MCP can be extended to run bulk updates and other content management tasks.

           
            kautuk_sahni
            Community Manager
            kautuk_sahniCommunity Manager
            Community Manager
            April 1, 2025

            @sandeep-l Did you find the suggestions helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!

            Kautuk Sahni
            S
            Adobe Employee
            Sandeep-LAdobe EmployeeAuthorAccepted solution
            Adobe Employee
            April 4, 2025

            @kautuk_sahni- After multiple discussions, the requirements were updated to exclude the 'on-deploy' scripts.
            Consequently, these scripts were removed, leading to the bundle operating as expected!!

            Thanks!

              Terms & ConditionsAccessibility statement

              Loading footer...