The Goal at Start
Set up SAP Commerce + Composable Storefront locally and integrate the UI Boilerplate to experiment with theming and a color-parser PoC.
In reality, the journey looked more like:
Commerce Initializr showing: Initializr version: unknownFeatures reported as “unknown”discoverPackages failingUI Boilerplate not integratingTrying the ui-boilerplate-demo repo and hitting yarn install → 401 Unauthorized
The Journey Afterwards
1. Why I moved to Initializr 5.5.x or above
My initial setup used an older .tar.gz version of Initializr, which resulted in errors like:
Initializr version: unknown
Task ‘upgradePackages’ not found
Project contains configuration for unknown feature(s): ui-boilerplate, ui-boilerplate-grid
Execution failed for task ‘:discoverPackages’
Some commands ran, but not in a stable or predictable way.
To resolve this,
Move to Initializr 5.5.x or 5.6 (5.5.0 or newer from the release)Fix global configuration (package discovery & certificates)Only then attempt optional features like UI Boilerplate
Installation instructions are here:
🔗https://pages.github.tools.sap/cx-innovation-projects/commerce-initializr/5.5.1/#/configuration/global-config
After installing, set up your local environment credentials in local.toml.
2. Package discovery on 5.5.x shows some errors — and that’s expected
Even on 5.5.0, running:
initializr-orchestrator discoverPackages
may still show warnings or manifest-related errors.
These do not impact the buildThe task should not fail entirelyYou can safely continue to project generation
Running:
initializr-orchestrator packages
gave clean, successful output:
Initializr version: 5.5.0
A new stable version is available: 5.5.1
### Initializr Packages ###
initializr-core (INSTALLED | LOCAL-ONLY)
This confirmed my setup was correct. Make sure to run the commands in accurate manner and double check your initializr version response in command shell.
3. Fixing the PKIX Error (if you see it)
If you get a PKIX path building failed error during package discovery, just import your corporate CA into the Java truststore: sudo keytool -importcert -trustcacerts
-keystore $JAVA_HOME/lib/security/cacerts
-storepass changeit
-alias commerceca
-file organizationTrustedCertEntry.cer
What I learned (and what I parked for later)
Things that now work reliably
Clean Initializr 5.5.x installationVersion correctly visible in terminallocal.toml for credentialsconfig.toml for global behaviour & discoveryCertificates imported (fixing PKIX errors)discoverPackages completing with only harmless warningsinitializr-orchestrator packages returning valid resultsSuccessful project generation:projectInfoinstallDependenciesgenerateProject./gradlew setup
⏸Things I parked for Part 2
Using UI Boilerplate via Initializr featuresRunning ui-boilerplate-demo without internal npm/Yarn registry issues
📝Final Note
With Initializr 5.5.x and correct local/global configurations, the setup is finally stable—good enough to continue with Commerce + Spartacus.
Anyone can follow UI Boilerplate exploration now.
Links related to UI BoilerPlate installation: https://pages.github.tools.sap/cx-innovation-projects/ui-boilerplate/#/uib/getting-started/installation
The Goal at StartSet up SAP Commerce + Composable Storefront locally and integrate the UI Boilerplate to experiment with theming and a color-parser PoC.In reality, the journey looked more like:Commerce Initializr showing: Initializr version: unknownFeatures reported as “unknown”discoverPackages failingUI Boilerplate not integratingTrying the ui-boilerplate-demo repo and hitting yarn install → 401 UnauthorizedThe Journey Afterwards1. Why I moved to Initializr 5.5.x or aboveMy initial setup used an older .tar.gz version of Initializr, which resulted in errors like:Initializr version: unknown
Task ‘upgradePackages’ not found
Project contains configuration for unknown feature(s): ui-boilerplate, ui-boilerplate-grid
Execution failed for task ‘:discoverPackages’Some commands ran, but not in a stable or predictable way.To resolve this,Move to Initializr 5.5.x or 5.6 (5.5.0 or newer from the release)Fix global configuration (package discovery & certificates)Only then attempt optional features like UI BoilerplateInstallation instructions are here:🔗https://pages.github.tools.sap/cx-innovation-projects/commerce-initializr/5.5.1/#/configuration/global-configAfter installing, set up your local environment credentials in local.toml.2. Package discovery on 5.5.x shows some errors — and that’s expectedEven on 5.5.0, running:initializr-orchestrator discoverPackagesmay still show warnings or manifest-related errors. These do not impact the buildThe task should not fail entirelyYou can safely continue to project generationRunning:initializr-orchestrator packagesgave clean, successful output:Initializr version: 5.5.0
A new stable version is available: 5.5.1
### Initializr Packages ###
initializr-core (INSTALLED | LOCAL-ONLY)This confirmed my setup was correct. Make sure to run the commands in accurate manner and double check your initializr version response in command shell. 3. Fixing the PKIX Error (if you see it)If you get a PKIX path building failed error during package discovery, just import your corporate CA into the Java truststore: sudo keytool -importcert -trustcacerts
-keystore $JAVA_HOME/lib/security/cacerts
-storepass changeit
-alias commerceca
-file organizationTrustedCertEntry.cerWhat I learned (and what I parked for later)Things that now work reliablyClean Initializr 5.5.x installationVersion correctly visible in terminallocal.toml for credentialsconfig.toml for global behaviour & discoveryCertificates imported (fixing PKIX errors)discoverPackages completing with only harmless warningsinitializr-orchestrator packages returning valid resultsSuccessful project generation:projectInfoinstallDependenciesgenerateProject./gradlew setup⏸Things I parked for Part 2Using UI Boilerplate via Initializr featuresRunning ui-boilerplate-demo without internal npm/Yarn registry issues📝Final NoteWith Initializr 5.5.x and correct local/global configurations, the setup is finally stable—good enough to continue with Commerce + Spartacus.Anyone can follow UI Boilerplate exploration now. Links related to UI BoilerPlate installation: https://pages.github.tools.sap/cx-innovation-projects/ui-boilerplate/#/uib/getting-started/installation Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
