Workspace path prefix removed from content blobs archive

The "workspace" path prefix has been removed from the content-blobs archive. To add the blobs to the Blueprint workspace, extract the archive above the cloned workspace.

(CMS-15899)

Build Error After Disabling E-Commerce Extensions

After disabling all E-Commerce extensions as described in the Blueprint Developer Manual, the Maven build failed with an Enforcer error:

[WARNING] Rule 1: com.coremedia.maven.enforcer.ModularOneRepoEnforcerRule failed with message:

    Dependencies into another workspace should use the respective workspace bom to manage the versions: lc-ecommerce-ibm-cae in C:\coredining-migration\workspace\apps\cae\cae-blueprint-bom\pom.xml
    Dependencies into another workspace should use the respective workspace bom to manage the versions: lc-contentbeans-api in C:\coredining-migration\workspace\apps\cae\cae-blueprint-bom\pom.xml
    Dependencies into another workspace should use the respective workspace bom to manage the versions: lc-contentbeans-impl in C:\coredining-migration\workspace\apps\cae\cae-blueprint-bom\pom.xml

...
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M2:enforce (enforce-onerepo-rules) on project cae-blueprint-bom: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]

This was caused by Headless Server still having a dependency on some module of a Commerce extension, which was then no longer managed (actually, not even available). The issue has been fixed by introducing an extension point for headless-server and moving the Headless Server module that needs Commerce into the lc-asset extension. Now, disabling lc-asset also disables Commerce support in Headless Server.

(CMS-15892)