@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...

@arunpatidar  Thanks for cross-checking. I thought the same thing initially. Then realized, that OOTB core pom.xml is inheriting <groudID> from parent pom, but still... Not part of symbolic name   Also, tried placing it in core/pom.xml. But, no luck    

Hello,   We have refractured legacy code as per the Archetype 48. In the latest code, groupID is missing from Bundle Symbolic name. Only Artifact ID is used in Symbolic Name. What could we be missing? Please suggest.

@AnubhavGu    Publishing metadata is not pushed to publish instances.  For any new pages, the jcr:created on publish should be equal to publish date. I am hoping the same when pages are published again.   Incase, neither jcr:created nor modified (on Publish) are in sync, the we might need to create ...

@HARPREETSI5    We need to integrate with Adobe Sensei for Smart Tagging. Details for on-premise/AMS are available here: https://techrevel.blog/2019/10/21/smart-tags/   For Enhanced Smart tags training, please refer to https://experienceleague.adobe.com/en/docs/experience-manager-64/assets/managing/...

@abhishekanand_    Thanks for sharing the Article.  "acs-commons/granite/ui/components/include” I have used it for Component Dialogs. Does it also work with component policies?

@EduardoBo3    We can share a policy for a "component across multiple templates" or "multiple occurrences of same component on a template". But, we cannot share parts of it like just the Style System. It can be shared only as a whole.   While creating a new policy we can duplicate an existing one an...

@nsvsrk    Once DM integration is set-up with AEM, you would need to set up the necessary Image Profiles for Smart Crop and Image Presets for Smart Imaging. Apply these to the relevant AEM Asset folders. Once image is uploaded, it would be synced to DM as well.  Select the image and check renditions...