In AEM Adobe Granite HTMl Library manager there are a lot of configuration options.
I would like to know what htmllibmanager.excluded.path.list.name is being used for.
2
votes
2 Answers
2
votes
The htmllibrarymanager has a node listener that checks for client libs under certain path. This trigger is responsible for merging and compaction of clientlibs (if enabled) for the pages. The exclude path (like the name says) skips the listener's handling of these concatenation and compaction tasks. It is normally configured to exclude pre-compiled scripts in AEM and cloud products.
1
votes
The HTML Library Manager uses a JCR Event Listener purely for the purpose of cache invalidation, i.e. when the file at /apps/myco/clientlib/js/somefile.js, it knows to invalidate the cached client library which contains this file (presumably /apps/myco/clientlib). The configuration htmllibmanager.excluded.path.list.name defines a set of paths under which events are not observed. It has nothing to do with minification or concatenation in the sense that if you were to create a client library under any of the excluded paths, it would still get concatenated and minified (depending on the configuration).
You should not change this value. It is listed on https://docs.adobe.com/docs/en/aem/6-3/develop/ref/javadoc/deprecated-configurations.html as to be changed only by Adobe. And if you do change it (which again, you shouldn't), you definitely shouldn't change it to include any paths which may contain client libraries as that would result in stale cache entries.
