Regeneration and file ownership

Regeneration replaces generator-owned files while preserving established business and customization files.

When to use

Use this reference when generating, reviewing or operating a Service Architect project.

A missing file is always added.
A basename containing generated is overwritten and receives the incoming file mode.
A path listed in scripts/merge-overwrite.txt is overwritten even when its public filename cannot contain generated.
Every other existing file is preserved as a user-owned extension point.
Local generated files missing from a new archive are reported as STALE but are not removed by a normal merge.
After merging, the validator checks that generated interfaces still find the preserved business makers.

Statuses printed by merge-check and merge.generated.sh.

StatusOwnershipDescription

ADDNew file

The destination did not exist and the archive file is copied.

UPDGenerated file

An existing generated-basename file is replaced.

OVROverwrite list

An exact path from merge-overwrite.txt is replaced.

SKPUser owned

An existing extension file is preserved.

STALELocal generated

A local generated file is absent from the incoming archive; normal merge keeps it.

make merge-check ARCHIVE=/tmp/example.zip
make merge ARCHIVE=/tmp/example.zip
make merge-validate
cat .servicegen/merge.log