@siva_vjwd    We have recently migrated from 25 to 47. Here are the pointers we had to work on: Move the code in right modules based on  https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/aem-project-content-package-structure We are updating d...

@arunpatidar @BrianKasingli    I received following response from Adobe. Thought of sharing, if anyone refers to the thread in future   "To address your query about which Maven plugin is recommended by Adobe for handling OSGi bundles in AEM projects, let's look into the details of both plugins you m...

Thanks for raising it @content_publisher It would be incredibly helpful to Marketers.

@karthik-elumalai    It may not be possible to define order of installation. Safer approach might be to create separate packages. 200 models in a config seems to be a lot. Do they follow any structure which can help you define filters?

@Manasi29    Set a new AEM InstanceInstall SP... I am using 18Wait for logs to stabilize.Check all bundles are active.Verify various AEM links. You should be able to access pages. Always stop AEM gracefully, before restarting your system

Thanks for sharing the link and details @arunpatidar 

@raju-komari    You can cancel the current Activation by going to Workflow>Instances. Its should look like the image I shared in previous comment. And then you can Activate the Image alone via "Manage Publication" option.   If you have suggestions to further improve the experience, please submit the...

@AKurtulush    It seems your HTL is importing a java class (may be a Sling Model) which is not available. Please build the core bundle firstAssure that these imports are available. Best to check via the bundle information in /system/console/bundles/<your bundle>Build the apps module which is causing...

@arunpatidar @BrianKasingli  Thanks for the inputs.   Just observed that its caused by following plugin. Its the default plugin in latest archtypes <plugin> <groupId>biz.aQute.bnd</groupId> <artifactId>bnd-maven-plugin</artifactId> <executions> <execution> <id>bnd-process</id> <goals> <goal>bnd-proc...

@raju-komari    If its working the way you have described, it seems to be well designed. The users should see what was scheduled for publish. When we schedule for later, a workflow instance is created. A new version is created and the replication payload is this specific version of an asset (as visi...