Replies

Highlighted

Avatar

Avatar

daniel379379

Avatar

daniel379379

daniel379379

22-06-2018

arunp99088702

As unsaid Arun: ((((

That field "Long term client side cache key" is related to the next field "Long term cache key format", which by default is "lc-% s-lc". And these two settings combined change the name of the file in "{filename}.lc- {timestamp}-lc.min.css" (e.g.: main.lc-9484393.min.css). This solution was not what I need and it creates also obvious caching problems, because the css inclusion is in the head, so for every css/js update in production, I should clear the entire cache of my site on dispatcher.

So the problem has remained unresolved, these damn ClientLibraries are not invalidated.

D.

Highlighted

Avatar

Avatar

pradeepn6086740

Avatar

pradeepn6086740

pradeepn6086740

18-07-2018

Hey did you find any solution for this.

Thanks,

Pradeep

Highlighted

Avatar

Avatar

aemmarc

Employee

Avatar

aemmarc

Employee

aemmarc
Employee

18-12-2018

Everyone is looking at this the wrong way.

In AEM 6.3 and 6.4 the client libraries are persisted on the file system. They no longer live under /var

Under one of the bundles (bundle248 on my local) there is an outputcache directory. Within this directory is where the compiled client libraries live.

For example on an AEM 6.3.3.0 instance:

\AEM 6.3\6.3.3.0\crx-quickstart\launchpad\felix\bundle248\data\outputcache

\apps

\etc

\libs

This is all documented here : How to force a recompilation of all Sling scripts jsps, java, and sightly in AEM 6.4

Highlighted

Avatar

Avatar

rodnal

Avatar

rodnal

rodnal

08-05-2019

Thanks for this answer you helped me a lot.