AEM 6.5 - Using ACS AEM Commons as a dependency

[#1]

I have been following the documentation on https://adobe-consulting-services.github.io/acs-aem-commons/pages/maven.html

We are upgrading AEM from 6.3.3.7 to 6.5.5. The acs-aem-commons package works sweet in AEM 6.3 through code POM dependencies and we are using shared component properties as an example. 

I have used Archetype 23 to migrate code to new structure however I am not planning on using ui.content package as I have pretty much all I need in /core, /ui.apps, /ui.frontend(.react) project.

Am I supposed to be using ui.content package just to include acs aem commons dependency in the project or I am missing something here?

Is there any other way I can include ACS AEM Commons in my AEM 6.5 project? I really want to avoid manually installing the package on my author/publisher. 

[#2]

Adding ACS Commons in the AEM project as Maven build works as is by following the steps in https://adobe-consulting-services.github.io/acs-aem-commons/pages/maven.html
As described in this document, for archetype 21 and above its recommended to use "all" project module to embed ACS commons in the project.
Its just that we need to replace the 

<target>/apps/my-app-packages/application/install</target>

<target>/apps/my-app-packages/content/install</target>

 with your package name as 

<target>/apps/<<package-name>>/content/install</target>

<target>/apps/<<package-name>>/application/install</target>