ACS AEM Commons Implementation for Inhouse AEM 6.5 Instance

[BinaryAlchemy11]

I have a requirement for the ACS AEM Commons implementation for AEM Inhouse Instance. I wanted to know the best practices on how it can be implemented and the impact it might have on the existing code/libraries that has been currently used. The goal is to have the most stable version of ACS AEM Commons installed with really less or no impact to the current code and library.

If any one has recently implemented the ACS AEM Commons to the their instance, any recommendation or lookout on the issues would definitely help.

[narendragandhi]

Hi @BinaryAlchemy11 

Please refer this page for the compatibility of ACS AEM Commons version and also features for an AEM Inhouse instance - https://adobe-consulting-services.github.io/acs-aem-commons/pages/compatibility.html

Hope this helps!

Thanks

Narendra

[BinaryAlchemy11]

I have seen this link for compatibility before. As mentioned above, I want to know more on the best practice and things that I have to look out (errors/issues) while installing the ACS AEM Commons to the AEM Inhouse Instance. 

 Also, would like some suggestions if anyone has experience on installing inhouse.

[narendragandhi]

Thanks for the details. If you could also mention your AEM version, Service Pack version and whether you are using JDK 8/11 others could comment on their observations. 

Checking the filter.xml for different modules in ACS Commons can help you confirm the impact to existing code.

Thanks

Narendra

[BinaryAlchemy11]

I am using these Version:

AEM 6.5.20

Java(TM) SE Runtime Environment(build 11.0.13+10-LTS-370)

[Shashi_Mulugu]

@BinaryAlchemy11 its all depends on what level of custom implementation you have in your instance. 

In general,  it will not break any OOTB features.

Please refer to general issues with ACS commons reported, search by your aem version

https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues