Projects created from master fail to deploy: template mapstore-services version not aligned by release workflows #13044

Description

A project created from master with createProject.js does not start: Tomcat refuses to deploy the war.

More than one fragment with the name [spring_web] was found

The standard project template (project/standard/templates/pom.xml) still depends on mapstore-services 1.13-SNAPSHOT, while master is at 1.14-SNAPSHOT. The project gets Spring 7.0.8 from mapstore-services 1.13 and Spring 7.0.9 from the GeoStore war, so the war contains both versions of every Spring jar.

The template should be aligned automatically by the release workflows (cut_major_branch.yml, pre_release.yml, post_release.yml), but they run mvn versions:set-property on project/standard/templates/web/pom.xml. The mapstore-services.version property lives in project/standard/templates/pom.xml since #10015, so the command does nothing and the template has to be aligned by hand at every release (#12708, #12711, #12731).

Moreover, the project documentation does not say that INITIAL_ADMIN_PASSWORD must be set before npm start, and the documentation only shows how to set it on Linux.

How to reproduce

1. Run node createProject.js from master and create a standard project
2. Run npm start (or mvn clean install and mvn cargo:run -f ./web/pom.xml) in the project
3. The mapstore webapp fails to deploy with the error above

Expected Result
The project starts, and the admin user can log in with the password set in INITIAL_ADMIN_PASSWORD.

Current Result
The webapp is not deployed.

• Not browser related

Pull requests

• Fix release workflows not updating project template version and more #13040 fixes the release workflows and the documentation (to backport on 2026.03.xx)
• Align standard pom template mapstore-services.version to 1.14-SNAPSHOT #13043 aligns the template on master to 1.14-SNAPSHOT (master only, stable branches keep their own version)