The DTM cloud service in AEM gives an option to include production scripts on author and an option to include staging script on author and production script on publish. I have a requirement to include staging scripts always(for both author and publish) in lower environments (DEV, QA, Stage) and prod...

Then why out of the box image component uses URLs relative to the current page ? 

What are the pros and cons of using absolute image paths vs the paths relative to the current page node (What image component uses. )Example -   /content/dam/site/asset/jcr:content/renditions/dam_web.png  (This uses direct DAM URL to render the image)                            OR                   ...

Is there any update on this ? 

I would suggest to configure the URLs in run mode specific OSGI configuration nodes. And then you can read those variables in the page head.jsp and render them as global variables inside the <script> tag.  The JS file can simply use these variables to fetch the URLs value. 

I found that the commerce.api package is exported by the cq-commerce-core bundle in 6.2. There is no separate bundle which exports the commerce API. Therefore, you can try with the following dependency in your project- <dependency> <groupId>com.adobe.cq.commerce</groupId> <artifactId>cq-commerce-cor...

There is a package installation mode "merge" for these type of use cases. http://www.wemblog.com/2012/04/how-to-change-package-install-behavior.html.If your requirement is to only import ACL definitions from another instance then try the following tool - https://adobe-consulting-services.github.io/a...

I do not think there is anything to do with Uber Jar as you are able to compile your code. The exception you see is a run time exception when you execute your workflow process. Check in the Apache felix console whether the process step component class is in active state or not. If you do not see the...

It seems that there is a node in your publish AEM instance which is in checked in state. Log the path of the node before you update any properties in the code. And then you can checkout the node manually using crx/explorer and try again. See the attached screenshot. 

You can refer the following project on github - https://github.com/pcfens/puppet-aem