How to override an OOTB bean file in CCV2?

[Huskar]

If I want to customize a bean file (say a form which is not generated via beans.xml), we can place the form inside config/customize folder and run ant customize so it can be moved to appropriate folder inside bin. But in CCV2 why do we use _CUSTOMIZE_ folder? Doesn't it duplicate the code? Why don't we have common location for customize code to be used in local development and CCV2 development as well?

Is there any specific reason for the same?

[adambadura · Accepted solution]

Hi,

Where is _CUSTOMIZE_ folder documented?

The official documentation says that config/customize is not supported and suggests to use build callbacks instead:

https://help.sap.com/docs/SAP_COMMERCE_CLOUD_PUBLIC_CLOUD/1be46286b36a4aa48205be5a96240672/b35bc14a6... :

SAP Commerce Cloud implements a fixed build process, so you can't run ant
customize or change files inside a Commerce release.

However when you look at the build log it seems that ant customize is actually executed:

2023-08-04 15:58:07,608 INFO d.h.c.c.t.BuildCoreCommerceTask [main] Applying customize dir
2023-08-04 15:58:07,609 INFO d.h.c.c.BuilderPlatformAntExecutor [main] Ant path: /opt/workspace/build/commerce-suite/hybris/bin/platform/apache-ant/bin/ant
2023-08-04 15:58:07,609 INFO d.h.c.c.BuilderPlatformAntExecutor [main] Fixing ant permissions
2023-08-04 15:58:07,609 INFO d.h.c.e.Executor [main] Executing [/opt/workspace/build/commerce-suite/hybris/bin/platform/apache-ant/bin/ant, customize] in /opt/workspace/build/commerce-suite/hybris/bin/platform, envs = ...

It is possible that this is kept for backward compatibility.

Regardless I would try to minimize the dependence on ant customize since it looks like SAP may want to remove it in the future.

[Huskar · Accepted solution]

You can find info related to _CUSTOMIZE_ here: https://me.sap.com/notes/0002821884.

1. Also just wanted to ask, this log that you pasted here, is it fromCCV2 deployment?
2. If I modify buildcallback.xml of my extension and configured the step for before build, will it work? Like we don't have to necessarily modify the platform -> buildcallback.xml?

[adambadura · Accepted solution]

Thanks for the link, I did not know that.

Regarding your question:

1. Also just wanted to ask, this log that you pasted here, is it fromCCV2 deployment?

Yes, I copied it from a sample build on CCV2.

2. If I modify buildcallback.xml of my extension and configured the step for before build, will it work? Like we don't have to necessarily modify the platform -> buildcallback.xml?

Yes, this is exactly what happens in the example from help page - they modify buildcallbacks.xml of the custom extension myextension and copy custom files there.