repository-patch

/repository-patch — Repository Patch Generator

In-Process SDK only — repository patches deploy inside the ACS JVM as part of the Platform JAR. They differ from bootstrap loaders (/bootstrap-loader): a patch migrates existing data between module versions; a bootstrap loader creates initial data on first install.

Generate an Alfresco repository patch that migrates data or structure exactly once per repository, recorded permanently in alf_applied_patch.

Input

Read REQUIREMENTS.md to identify patch requirements:

1. Resolve the Platform JAR project's Root path from Section 2 (Project Architecture).

   • If Section 2 contains no Platform JAR project, stop and explain that /repository-patch only applies to the in-process Platform JAR project.

2. Read Section 7 (Behaviour Requirements) sub-section "Repository patch requirements".

   • If no patch requirements are present in Section 7, stop and ask the user to run /requirements first (or provide a description as $ARGUMENTS).

3. From Section 2, derive:

   • {platform-project-root} — . for Platform JAR only mode; {name}-platform/ for Mixed mode
   • {module-id} — the Platform JAR artifactId (bare artifact ID, e.g. my-extension). Read from <artifactId> in the platform pom.xml or derive as {platform-artifactId} from Section 2. Never use the full module.id property value as the directory name.
   • {java-package} — the Java package declared in Section 2
   • {prefix} — the namespace prefix declared in Section 5 (Content Model Requirements)

4. Derive from patch requirements:

   • {PatchName} — PascalCase patch name (e.g. AddWebableAspect, RenameArchiveFolder)
   • {patch-id} — globally unique dot-notation patch ID: patch.{module-id}.{camelCaseName} (e.g. patch.my-extension.addWebableAspect)
   • {fixesFromSchema} — the ACS DB schema version from which this patch applies (inclusive)
   • {fixesToSchema} — the ACS DB schema version up to which this patch applies (inclusive)
   • {targetSchema} — the ACS DB schema version after which this patch is recorded as applied; for ACS 26.1 use 5026
   • Which Alfresco services the patch needs beyond the default set (nodeService, searchService, transactionService, namespaceService are injected by basePatch automatically)