3699200 - OOTB file replacement via buildcallbacks.xml did not take effect due to image reuse

• A custom extension defines OOTB file replacement in its buildcallbacks.xml (for example, deleting an OOTB class and copying a custom class), but the replacement does not occur even though the build finishes successfully.
• Expected build log lines indicating the custom extension build and callback execution are missing. Typically you would see:
  • INFO ... [echo] building extension 'your-extension'...
  • INFO ... [echo] ###### !!!! Replacing ...
• Instead, the build log is unusually short and dominated by messages such as:
  • INFO d.h.c.i.h.g.HashGeneratorUtils [main] Skipping generating hash from file: ...
• No "Replacing …" echo output appears, and no evidence that the custom extension buildcallbacks.xml ran.
• Similar behavior is described in KBA 3227748 – Commerce Cloud build does not contain custom changes/commits (referenced for context).

SAP Commerce Cloud

SAP Commerce Cloud, Replacing OOTB Files, replace, OOTB file, OOTB class, build, image reuse, selective images rebuild, disableImageReuse, buildcallbacks.xml, OOTB file replacement, custom extension, Builder policy, hash, Skipping generating hash from file, custom changes not applied, callback not executed, platform image reuse , KBA , CEC-SCC-CLA-BUI , Build Process , Problem