You may use this tool or refer its source code for your requirements -Renovator

As far as I know, the sequence of installation doesn't matter and it should point to /libs to utilize the updated features.It would work with /etc as well but not sure if the behavior would be different.Try this -Use /etc path and add slingResourceSuperType to /etc path node and point it to /libs pa...

The way I read your problem statement is that the mentioned behavior exists on publish server. I'm missing the point that why would you want to create the versions on publish server. I'm not able to think of any use case. To me versioning belongs to author and not publish server.I would recommend th...

Per link that you shared, the bug is fixed and released. You may install latest package, clear internal cached libraries and test otherwise, open a ticket similar to the link that you shared.Releases · Adobe-Marketing-Cloud/asset-share-commons · GitHub HTH

Probably versioning is turned on for that node/page/asset. Check that as well.

Use this - Maven Repository: com.adobe.aemfd » aemfd-client-sdk » 6.3.0  orIndex of /repositories/public/com/adobe/aemfd/aemfd-client-sdk/6.3.0

I tested this and it worked fine. As Scott mentioned use encode/decode as applicable.output:{":type": "weretail/components/content/text","message": "some junk characters test=€ , Š , Œ , ™ , š , œ , ž{}[]<>=-()@#$&*"}acs-aem-samples/SampleComponentExporter.java at master · Adobe-Consulting-Services/...

You are using a domain/apache/dispatcher in front of this server. Could you check 1) that the configurations do not block you and allow to pass through2) share relevant dispatcher logs and server logs3) you have appropriate read/write permissions

I think the screenshot/error message above is related to workbench integration and not with AEM.AEM's error.log is located in the installation directory under logs folderpath:  <aem-setup-folder>/crx-quickstart/logs/....check if this link helps - Upgrade Procedure You may create a script (sh/bat) fi...

In the meanwhile, check if your exporter code and jar versions are appropriatecheck these reference examples -acs-aem-samples/SampleSlingModelExporter.java at master · Adobe-Consulting-Services/acs-aem-samples · GitHub Adobe Experience Manager Help | Exporting Adobe Experience Manager Data Using Sli...