can you describe the problem in more detail?
is the ACS versionion clientlibs feature broken when the Clientlibs UI Extensions is only deployed to the same system, or does those two just not work together when you try to include a versioned clientlib using the "/apps/wcm-io/wcm/ui/clientlibs/sightly/templates/clientlib.html HTL script from wcm.io?
The two do not work together. Ideally, it should only add attributes to the existing clientlib output.
the "ACS AEM Commons Versioned Clientlibs" feature seems to be somewhat deprecated, they added a banner that's it no longer compatible with the latest AEM version (AEM as a Cloud Service incompatible). see also discussion here: #183.
that there is an OOTB solution in AEM available for quite a long time (since AEM 6.2?) by either specifying a "longCacheKey" property in the clientlib definition (e.g. with a version number automatically set during build time), or by defining a "Long term client side cache key" centrally in the osgi configuration in the "Adobe Granite HTML Library Manager".
so i currently think it's not worth investing more time in making those two compatible (PR's welcome, though). i've not digged into the details, but afaik the versioned clientlib feature form ACS AEM commons works as rewriter on the generated HTML output, so i'm not sure why it should not work together with the output generated by Clientlibs UI Extensions; maybe it's just an issue of properly configuring the rewriter pipeline.
btw, this "longCacheKey" feature is very poorly documented, i've found some public available references to it in
we are using it in our project for years, you can also use our maven archetype to setup a project which used the maven project version and current git has as a version for the clientlibs
Super helpful. Thanks, Stefan!!