dont put * (import everything ) in Import-Package

certain libraries or tools might have compatibility issues, which can lead to unexpected behavior.As ACS commons is open source, you can raise an issue here  - https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues 

You can try This : https://experience-aem.blogspot.com/2023/06/aem-cloud-service-multiple-composite-multifields-in-content-fragment-editor.html 

you need to add includeresource after Export-Package Example :  <plugin> <groupId>biz.aQute.bnd</groupId> <artifactId>bnd-maven-plugin</artifactId> <executions> <execution> <id>bnd-process</id> ...

It can't be automatically. someone did it mistakenly. someone might be using shell window to edit the farm file and by mistake deleted everything.ORyour cloud manager deployment code is having blank farm file that is getting replaced while deploying the code. 

you don't need to develop any login page or components for login and creating account of the user in AEM.AEM Supports SAML 2.0, In which you need to configure IDP details, certificate, user profile properties mapping with SAML assertion, User group assignment etc.  Once SAML configuration will be do...

Here's a general outline of the steps and skills you might need to develop:Product Management Fundamentals: Develop a deep understanding of product management principles, including market research, customer needs analysis, roadmap planning, and prioritization.AEM Knowledge and Experience: Gain a tho...

try using below 2 properties and then check.  props.put("dam:imageServerAsset", true); props.put("dam:assetState", "processing"); 

This feature is not supported for publish and in near future also there is no road map for this.

Hi,Please check https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-4-oauth-2-legged-authorization/td-p/327442