If you would like to add a JS file to an AEM page without using a client library then you can add it to the page component code with a <script> tag (as you would with normal HTML).

Hi sr508​ java package com.day.cq.dam.core.impl is not exported by the out of the box cq-dam-core bundle.  So any classes in there are internal, as such, they cannot be added to the uber jar.

I checked the product code, it seems that the NullPointerException indicates that the cq:lastReplicationAction property is set on the node you are publishing but not the cq:lastReplicated or cq:lastPublished.  That shouldn't be possible under normal circumstances.  Do you have some custom code that ...

Please provide more details on what you are trying to cache.  /ignoreUrlParams would just ignore the source parameter and cache the file (minus the querystring).Are you trying to cache varying versions of the same page / html by querystring param source?

There are a few blog posts I was able to find that cover this:Experiencing Adobe Experience Manager - Day CQ: AEM 64 - Touch UI Nested Composite Multifield Using Coral 3 http://www.aemcq5tutorials.com/tutorials/create-touch-ui-nested-multifield-dialog-aem/ Did you happen to try those already?

Hi Chamu,This issue with namespace errors usually happens after a selective crx2oak migration.  You have solved the issue properly, see here for the official doc on the topic:javax.jcr.NamespaceException: Unknown namespace prefix error in AEM Thanks,Andrew

Please try this solution out on your publish instance: 1. Go to http://hostport/system/console/configMgr2. Search for and open Apache Sling Authentication Service3. Add these two entries to the sling.auth.requirements-/etc.clientlibs-/etc/clientlibs/granite4. After changing the property, restart the...

Hi Uma,Please provide more specific details like error messages, your ant build script and any other information required to understand the problem.  There could be many reasons for this to fail.Thanks,Andrew

Regarding the "Netscape Comment" issue, your certificate shouldn't contain any of the netscape related extensions such as this:  X509v3 extensions:       Netscape Comment:           OpenSSL Generated CertificateTo generate the cert without that included you would need to modify the openssl.cnf file:...

I checked, the issue is product issue CQ-49206 which is fixed in AEM 6.4.