AEM 6.5 - Using ACS AEM Commons as a dependency

Avatar

Avatar
Validate 1
Level 1
aaykay22
Level 1

Likes

2 likes

Total Posts

12 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Applaud 5
Affirm 1
View profile

Avatar
Validate 1
Level 1
aaykay22
Level 1

Likes

2 likes

Total Posts

12 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Applaud 5
Affirm 1
View profile
aaykay22
Level 1

19-08-2020

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. 

View Entire Topic

Avatar

Avatar
Validate 1
MVP
Theo_Pendle
MVP

Likes

238 likes

Total Posts

251 posts

Correct reply

105 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 10
Ignite 1
View profile

Avatar
Validate 1
MVP
Theo_Pendle
MVP

Likes

238 likes

Total Posts

251 posts

Correct reply

105 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 10
Ignite 1
View profile
Theo_Pendle
MVP

19-08-2020

Hi @aaykay22,

The ACS Commons installation page you linked to contains the two steps you you need:

  1. Fetch the acs-aem-commons-content artifact via a maven dependency
  2. Embed that artifact into a package which you will then deploy

The documentation mentions "your content project’s pom.xml" but this is just a recommendation, there is no technical reason why this won't work in ui.apps, so you can just follow the documentation as-is and simply apply it to your ui.apps project 🙂

Disclaimer: if you have multiple AEM sites (tenants) running on a single instance, you may want to completely move the embedding of ACS Commons (and any other customization of the AEM platform) into a separate project. Check the architecture diagram in this tutorial: https://levelup.gitconnected.com/aem-multitenancy-running-multiple-websites-on-a-single-aem-environm... There are explanations too.