Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Fork WCM component to be organization core components

Avatar

Level 2

Hello Adobe friends,

 

Is it a practice to fork aem-wcm-core-components from github to be the organization’s core component? Therefore, it will be at the same level as wcm-core under /apps/core?

1 Accepted Solution

Avatar

Correct answer by
Employee

As mentioned in my previous comment, It's advised to use core components as dependency and overlay them to use. 

Forking is a decision you have to evaluate for your business use case, but consider the fact that you will not get any benefit from future releases of core components.

View solution in original post

0 Replies

Avatar

Employee

You do not need to fork the core component repo and maintain it. Rather, you can define dependency in your project POM, see this article for details [1], or you can download and install the core component package directly [2]

 

If you are using AEM as a Cloud Service, you do not need to define any installation step, as AEM as a Cloud Service automatically comes with the latest version of the Core Components [3]

 

Make sure that you do not use the core components directly, rather create proxy components [4]

 

[1] http://www.basef.com.br/index.php/Including_the_AEM_Core_Component_2.0_in_your_project

[2] https://github.com/adobe/aem-core-wcm-components/releases/tag/core.wcm.components.reactor-2.20.8 

[3] https://experienceleague.adobe.com/docs/experience-manager-core-components/using/get-started/using.h... 

[4] https://experienceleague.adobe.com/docs/experience-manager-core-components/using/get-started/using.h... 

Avatar

Employee

@blueboi you can fork the core component repo and maintain it as your company's core component. 

The only constraint in this approach will be that, you will not get any benefit from future releases of core components.

So take a decision carefully about which approach you want to proceed with.

Avatar

Level 2

Is this forking wcm-core a practice you think Adobe is evangelizing and telling organizations to do? Is there anybody from Adobe Tech team supports such?

Avatar

Correct answer by
Employee

As mentioned in my previous comment, It's advised to use core components as dependency and overlay them to use. 

Forking is a decision you have to evaluate for your business use case, but consider the fact that you will not get any benefit from future releases of core components.

Avatar

Level 9

@blueboi i dont think it is needed to fork core components. You can add below dependency in you project

 

<dependency>
<groupId>com.adobe.cq</groupId>
<artifactId>core.wcm.components.content</artifactId>
<type>zip</type>
</dependency>
<dependency>
<groupId>com.adobe.cq</groupId>
<artifactId>core.wcm.components.config</artifactId>
<type>zip</type>
</dependency>



<embedded>
<groupId>com.adobe.cq</groupId>
<artifactId>core.wcm.components.config</artifactId>
<type>zip</type>
<target>/apps/<project>vendor-packages/application/install</target>
</embedded>

. Add it in the "all" module of the project.  

Avatar

Level 2

But what if I would like to create my organization core components based on how wcm-core was built? Is it possible? Or should I better say, is it a good practice to fork wcm-core, rename it as organization-core-components and build new components from there.