Cloud Manager Build Issue - AEM as Cloud Service | Community
Skip to main content
Shashi_Mulugu
Community Advisor
Community Advisor
June 29, 2020
Solved

Cloud Manager Build Issue - AEM as Cloud Service

  • June 29, 2020
  • 2 replies
  • 1979 views

Hello Team,

 

I have a AEM project built using Archetype 23 and i have defined multiple content packages(ui.apps). i have same OSGI configurations defined in them. As per the earlier versions of AEM, OSGI will pickup based on order of runmodes. But with AEM as cloud, Build pipeline failing in Cloud Manager itself stating that conflict of OSGI configurations.

 

Where should i set this "'mergeConfigurations' flag to 'true'"?

 

Error:-

Configuration 'org.apache.sling.commons.log.LogManager.factory.config~test' already defined in Feature Model 'my_packages:aem-program-project.all:slingosgifeature:0.0.1-SNAPSHOT', set the 'mergeConfigurations' flag to 'true' if you want to merge multiple configurations with same PID

 

@kautuk_sahni @arunpatidar @kaushalmall 

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 kaushalmall

There are a couple of issues going on here. 

  • There is no “test” runmode in Cloud Service. Looks you have configurations under that runmode. Please read the Cloud Service documentation on which runmodes are supported 
  • This error is shown when you have multiple configs with the exact same PID in your code base and Cloud Service cannot determine which config to apply. Unfortunately, the error is a little misleading because the mergeConfiguration flag cannot be set as it says. 

If you remove your duplicate configs, it should work as expected. 

2 replies

kaushalmallAdobe EmployeeAccepted solution
Adobe Employee
June 29, 2020

There are a couple of issues going on here. 

  • There is no “test” runmode in Cloud Service. Looks you have configurations under that runmode. Please read the Cloud Service documentation on which runmodes are supported 
  • This error is shown when you have multiple configs with the exact same PID in your code base and Cloud Service cannot determine which config to apply. Unfortunately, the error is a little misleading because the mergeConfiguration flag cannot be set as it says. 

If you remove your duplicate configs, it should work as expected. 

Shashi_Mulugu
Community Advisor
Community Advisor
June 29, 2020
@kaushalmall I was able to run after removing duplicates but question is it was never an issue before as OSGI used to decide the priority but not expected to resolve during build time.
Adobe Employee
June 29, 2020

Hello ,

 

The build/deploy should work fine if we have only one config per PID across all the runmode configs. Please check by removing duplicate configs.

 

Regards,

Anubha