With this being fixed, config service is not automatically bounded. I have to manually open and bound it in OSGi config manager.I have immediate =true in the class@component(service =  ProviderABCConfigService.class, immediate = true )@Designate(ocd = ProviderABCConfigServiceImpl.Config.class)  

It was my mistake, in the other OSGi class  SomeOtherServiceImpl I have// @activate// protected void activate(ProviderABCConfigService config) {//// this.xyzConfig = config;//// }This was causing the issue, as soon as I comment this  build worked fine.Thanks for your help

It seems the above code is fine but whenever I try to use this in some class like@component(service = SomeOtherService.class, immediate = true)public class SomeOtherServiceImpl implements SomeOtherService {@reference  //  Or even @OSGIServiceprivate ProviderABCConfigService providerABCConfig;it retu...

Here is my interfacepackage com.xyz.aem.service; public interface ProviderABCConfigService {public String getProviderABCAppKey(); public String getProviderABCAppSecret(); public String getbDamPath(); public boolean isDisablePlugin() ; public String getProviderABCPath() ; public String getDropAccessT...

I am getting error when I deploy mvn project .  Non annotation type for activation object with descriptor (Lcom/xxx/sss/ssss;)V, type xxxxx -> [Help 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal biz.aQute.bnd:bnd-maven-plugin:5.1.2:bnd-process (bnd-process) on proj...