Hello All, we are facing circular dependency issue with ACS commons. I have embedded ACS commons as subpackage in my view bundle, but now acs commons is creating a dependency on my view bundle. So every time i deploy a new version of my code, ACS commons is keeping dependency on old versions also.
The challenge comes when we revert my code to previous bundle, ACS commons throw dependency error as it keep dependency on latest bundle which is no more available.
Did you set the acs commons dependency scope to provided ?
no, i havent used scope for this dependency as its not mentioned in ACS commons documentation
should i try with scope as provided ?
Yes try it
so i have tried adding scope as provided in view bundle's ACS dependency
Hi All, We are constantly seeing traversal node warnings in our logs. When we raised an adobe ticket they said it's because we are using ACS commons inbox feature and provided below Jira link Adobe-Consulting-Services/acs-aem-commons#1635
will there be any fix for the traversal nodes error in later versions... as of now we are using 3.17.0 version
Hello! We're using dispatcher 4.1.11+ and the ACS Commons Dispatcher TTL feature. We have some max ages sling:OsgiConfigs set for various regexes and a couple daily/monthly/weekly configs for expiration as well. What we're seeing, though, is a lot of requests where the expires header is defaulting to to January 1 1970. I've gone through the 3.13.0 code for ACS Commons (the version we're using) and I don't see anywhere that this header would be defaulted but wanted to check here to see if anyone know more.
Hello Everyone, I would like to check anyone worked on creating docker container for Author, publisher & dispatcher ...
@mrjayviper it should be there if you add a "Process step" from the sidekick to your workflow, then double click it to edit it, then go to the Process tab. In the Process dropdown, one of the options should be Send Templated Email. (If I couldn't find it, I'd try restarting the relevant bundle or the entire instance; if that still didn't work you could look into whether other workflow process options from AEM Commons were showing in the list)
Hi, New to ACS commons. Am trying to build the project but getting : [ERROR] Failed to execute goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.17:check (default) on project acs-aem-commons-bundle: Execution default of goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.17:check failed: Plugin org.codehaus.mojo:animal-sniffer-maven-plugin:1.17 or one of its dependencies could not be resolved: Failed to collect dependencies at org.codehaus.mojo:animal-sniffer-maven-plugin:jar:1.17 -> org.codehaus.mojo:animal-sniffer:jar:1.17.
Can someone help on this please
@mrjayviper I see what you mean about the documentation of the workflow step. It isn't clear to me, either. Maybe someone who has used this workflow step can assist you with these questions.