Build error on cloud manager | Community
Skip to main content
Level 2
October 5, 2022
Solved

Build error on cloud manager

  • October 5, 2022
  • 2 replies
  • 1715 views

Hi All,

 

We have a requirement to customize the acs commons and built some components based on that. We have built the components and included the entire project in our custom project as one module.

Once we push the code to adobe git and try to build it gives the below errors which are not in local.

Analyzing feature 'com.adobe.granite:aem-ethos-app-image:slingosgifeature:aem-runtime-application-publish-prod:1.0.0-SNAPSHOT' finished : 4 warnings, 1 errors.
[WARNING] [api-regions-exportsimports] com.adobe.aem.commons:assetshare.core:2.3.1: Bundle assetshare.core:2.3.1 is importing package(s) [acscommons.com.google.common.cache, com.adobe.cq.dialogconversion] without specifying a version range.
[WARNING] [api-regions-exportsimports] com.adobe.acs:acs-aem-commons-bundle:5.3.2: Bundle acs-aem-commons-bundle:5.3.2 is importing package(s) [com.amazonaws.services.s3, com.amazonaws.auth, com.github.benmanes.caffeine.cache.stats, twitter4j.json, twitter4j.auth, twitter4j.conf, twitter4j, com.amazonaws.services.s3.model, com.github.benmanes.caffeine.cache] without specifying a version range.
[WARNING] [configuration-api] Configuration org.apache.sling.commons.log.LogManager.factory.config~asset-share-commons: Property org.apache.sling.commons.log.pattern - Property is not allowed
[WARNING] [configuration-api] Configuration com.day.cq.mailer.DefaultMailService: Property smtp.port - Value 30001 does not match provided options
[ERROR] [api-regions-exportsimports] com.adobe.aem.commons:assetshare.core:2.3.1: Bundle assetshare.core:2.3.1 is importing package(s) [acscommons.com.google.common.cache, com.adobe.cq.dialogconversion] in start level 20 but no bundle is exporting these for that start level.
[ERROR] Analyser detected errors on feature 'com.adobe.granite:aem-ethos-app-image:slingosgifeature:aem-runtime-application-publish-prod:1.0.0-SNAPSHOT'. See log output for error messages.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 59.402 s
[INFO] Finished at: 2022-10-05T05:08:12Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.sling:slingfeature-maven-plugin:1.5.18:analyse-features (analyze-aggregates) on project aem-ethos-app-image: One or more feature analyser(s) detected feature error(s), please read the plugin log for more details -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
Removing intermediate container beabdd3d6fae
---> 1d5277ebc85a

 

Please help me if anything needs to be done before pushing the changes to adobe git ?

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 Singaiah_Chintalapudi

I would recommend to deploy the ACS packages manually. If you use Cloud Manager, it will complain about security vulnerabilities.

2 replies

Singaiah_Chintalapudi
Singaiah_ChintalapudiAccepted solution
Level 7
October 5, 2022

I would recommend to deploy the ACS packages manually. If you use Cloud Manager, it will complain about security vulnerabilities.

Level 2
June 4, 2023

How will you install this manually  ? 
ui.apps is immutable in remote instances, so it won't allow the package installations.
This has to go through code pipeline instead.

Saravanan_Dharmaraj
Community Advisor
Community Advisor
October 5, 2022

Does the same GIT branch used by Cloud Manager builds fine in your local without issues?

 

Singaiah_Chintalapudi
Level 7
October 6, 2022

Yes, this was working on our local codebase.