ngsllc · rmelarab-ngs · Aug 26, 2025 · Apr 2, 2025 · Apr 4, 2025 · Mar 5, 2025
diff --git a/.github/ISSUE_TEMPLATE/release_steps.md b/.github/ISSUE_TEMPLATE/release_steps.md
@@ -17,6 +17,9 @@ This steps have to be followed always when preparing a new release.
  - [ ] for `http_proxy`, check if [here](https://maven.geo-solutions.it/proxy/http_proxy/) is present the version specified. Release procedure is specified in the [Readme.md](https://github.com/geosolutions-it/http-proxy) file of the project.
  - [ ] for `mapfish-print` check if [here](https://maven.geo-solutions.it/proxy/http_proxy/) is present the version specified. Release procedure is specified in the [Readme.md](https://github.com/geosolutions-it/mapfish-print) file of the project.
 - [ ] Check if dependencies of MapStore libraries and geostore libraries are the same (compare `src/pom.xml` in geostore e `pom.xml` in MapStore).
+- [ ] Check if dependencies of the **template projects** are aligned
+  - [ ] `project/standard/templates/pom.xml` are aligned as the ones in `pom.xml` of MapStore
+  - [ ] `project/standard/templates/web/pom.xml` are aligned as the ones in `product/pom.xml` of MapStore.

 ## New stable branch creation

@@ -28,37 +31,37 @@ This steps have to be followed always when preparing a new release.
  - [ ] MapStore branch name to use: `YYYY.XX.xx`
  - [ ] use the default value for the other parameters
 - [ ] Wait for the process to complete. At the end:
-    - A Pull request will be created to the master
-    - A new branch named `YYYY.XX.xx` with fixed versions
+  - A Pull request will be created to the master
+  - A new branch named `YYYY.XX.xx` with fixed versions
 - [ ] Merge the incoming PR created by the workflow
 - [ ] Create on [ReadTheDocs](https://app.readthedocs.org/projects/mapstore/) project the version build for `YYYY.XX.xx` (click on "Versions" and activate the version of the branch)
 - [ ] Run the [`Cut Release Branch`](https://github.com/geosolutions-it/MapStoreExtension/actions/workflows/cut_release_branch.yml) workflow on MapStoreExtension project, indicating:
-    - [ ] Use workflow from branch `master`
-    - [ ] MapStore branch name to use: `YYYY.XX.xx`
-    - [ ] main branch `master` (default)
+  - [ ] Use workflow from branch `master`
+  - [ ] MapStore branch name to use: `YYYY.XX.xx`
+  - [ ] main branch `master` (default)
 - [ ] Update the [QA build](http://build.geosolutionsgroup.com/view/MapStore/job/MapStore/view/MapStore%20QA/job/MapStore2-QA-Build/) to point to the branch created (YYYY.XX.xx)

 ## Before the Release

 - [ ] Check `pom.xml` dependencies are all in fixed stable versions ( no `-SNAPSHOT` usage release). If not, You use the action  [`Update dependencies versions`](https://github.com/geosolutions-it/MapStore2/actions/workflows/update_dependencies_versions.yml) to fix them, setting:
-    - [ ] the branch to `YYYY.XX.xx`
-    - [ ] the of geostore, http_proxy and mapfish-print versions accordingly with the [MapStore release calendar](https://github.com/geosolutions-it/MapStore2/wiki/MapStore-Release-Calendars)
+  - [ ] the branch to `YYYY.XX.xx`
+  - [ ] the of geostore, http_proxy and mapfish-print versions accordingly with the [MapStore release calendar](https://github.com/geosolutions-it/MapStore2/wiki/MapStore-Release-Calendars)
 - [ ] Merge the PR created after the action avove has been finshed
- [ ] Check that [MapStoreExtension](https://github.com/geosolutions-it/MapStoreExtension) repository is aligned and working. 
+- [ ] Check that [MapStoreExtension](https://github.com/geosolutions-it/MapStoreExtension) repository is aligned and working.
 - [ ] Run the [Submodule Update](https://github.com/geosolutions-it/MapStoreExtension/actions/workflows/submodules_update.yml) of [MapStoreExtension](https://github.com/geosolutions-it/MapStoreExtension) to generate the `SampleExtension.zip` to use for testing.
-    - [ ] Use workflow from `YYYY.XX.xx` branch
-    - [ ] Wait for completition
-    - [ ] Download the `Artifacts.zip` that contains `SampleExtension.zip` from the execution of the `checks` action on the branch `YYYY.XX.xx`. This can be used for tests.
+  - [ ] Use workflow from `YYYY.XX.xx` branch
+  - [ ] Wait for completition
+  - [ ] Download the `Artifacts.zip` that contains `SampleExtension.zip` from the execution of the `checks` action on the branch `YYYY.XX.xx`. This can be used for tests.
 - [ ] Test on QA [https://qa-mapstore.geosolutionsgroup.com/mapstore/](https://qa-mapstore.geosolutionsgroup.com/mapstore/)
  - [ ] Test **everything**, not only the new features
  - [ ] Test the creation of a standard project starting in from the stable branch and with the internal backend, so:
-      - [ ] `node ./createProject.js` and insert the entries (for the rest simply press enter:
-          - **project name**: `release_project_test`
-          - **base branch**: insert the release branch (e.g. `YYYY.XX.xx`)
-          - **project folder** insert `../test_release_<release_number>` )
-      - [ ] `cd ../test_release_<release_number>`
-      - [ ] `npm install`
-      - [ ] `npm run start:app`, then check that an empty homepage loads correctly
+    - [ ] `node ./createProject.js` and insert the entries (for the rest simply press enter:
+      - **project name**: `release_project_test`
+      - **base branch**: insert the release branch (e.g. `YYYY.XX.xx`)
+      - **project folder** insert `../test_release_<release_number>` )
+    - [ ] `cd ../test_release_<release_number>`
+    - [ ] `npm install`
+    - [ ] `npm run start:app`, then check that an empty homepage loads correctly
  - [ ] Test [Binary](http://build.geosolutionsgroup.com/view/MapStore/job/MapStore/view/MapStore%20QA/job/MapStore2-QA-Build/) (take the mapstore2-<RELEASE_BRANCH>-qa-bin.zip, from latest build)

 ## Prepare Release
@@ -70,8 +73,8 @@ This steps have to be followed always when preparing a new release.
  - version to fix for the java module, accordingly with [release calendar](https://github.com/geosolutions-it/MapStore2/wiki/MapStore-Release-Calendars) (e.g. `1.7.0`)
  - use the default value for the other parameters
 - [ ] Wait for the process to complete. At the end:
-    - a new commit will be added to the release branch tagged as `vYYYY.XX.mm`. This commit will contain the changelog and the updated version of the java modules.
-    - a pull request will be created on master with the changelog updates
+  - a new commit will be added to the release branch tagged as `vYYYY.XX.mm`. This commit will contain the changelog and the updated version of the java modules.
+  - a pull request will be created on master with the changelog updates
 - [ ] Merge the incoming PR created by the workflow for updating changelog on Master
 - [ ] Run [`Submodules Update`](https://github.com/geosolutions-it/MapStoreExtension/actions/workflows/submodules_update.yml) on MapStoreExtension:
  - Branch `YYYY.XX.xx`
@@ -88,7 +91,7 @@ This steps have to be followed always when preparing a new release.
 - [ ] After "MapStore2-Stable-Build" finished, Launch [MapStore2-Stable-Deploy](http://build.geosolutionsgroup.com/view/MapStore/job/MapStore/view/MapStore%20Stable/job/MapStore2-Stable-Deploy/) to install the latest stable version on official demo.
      - `branch`: `vYYYY.XX.mm` (the version tag name, e.g. v2024.01.01)
      - `TAG_NAME`: `${branch}-stable` (tag of the docker hub image, previously build)
- [ ] Test the change has been applied, login on https://mapstore.geosolutionsgroup.com and verify that the layers from `gs-stable` are visible without errors (typically authentication errors that was caused by the wrong auth-key).
+- [ ] Test the change has been applied, login on <https://mapstore.geosolutionsgroup.com> and verify that the layers from `gs-stable` are visible without errors (typically authentication errors that was caused by the wrong auth-key).

 ## Create and Publish MapStoreExtension release

@@ -128,11 +131,11 @@ When the processes are finished, the release is ready to be published on github
 ## Finalize Release

 - [ ] Run the [`Post Release`](https://github.com/geosolutions-it/MapStore2/actions/workflows/post_release.yml) workflow on github with the following parameters:
-    - Use workflow from branch `YYYY.XX.xx` (the release branch)
-    - Version of Java Packages to restore accordingly with [release calendar](https://github.com/geosolutions-it/MapStore2/wiki/MapStore-Release-Calendars) with `-SNAPSHOT` E.g. `1.7-SNAPSHOT`
+  - Use workflow from branch `YYYY.XX.xx` (the release branch)
+  - Version of Java Packages to restore accordingly with [release calendar](https://github.com/geosolutions-it/MapStore2/wiki/MapStore-Release-Calendars) with `-SNAPSHOT` E.g. `1.7-SNAPSHOT`
 - [ ] Use the action  [`Update dependencies versions`](https://github.com/geosolutions-it/MapStore2/actions/workflows/update_dependencies_versions.yml) to restore the `-SNAPSHOT` version of GeoStore, setting:
-    - [ ] the branch to `YYYY.XX.xx`
-    - [ ] the of geostore, http_proxy and mapfish-print versions accordingly with the [MapStore release calendar](https://github.com/geosolutions-it/MapStore2/wiki/MapStore-Release-Calendars) and use `-SNAPSHOT` version of geostore.
+  - [ ] the branch to `YYYY.XX.xx`
+  - [ ] the of geostore, http_proxy and mapfish-print versions accordingly with the [MapStore release calendar](https://github.com/geosolutions-it/MapStore2/wiki/MapStore-Release-Calendars) and use `-SNAPSHOT` version of geostore.
 - [ ] Write to the mailing list about the current release news and the next release major changes
 - [ ] Optional - prepare a PR for updating release procedure, if needed
 - [ ] Close this issue

diff --git a/.prettierignore b/.prettierignore
@@ -1,19 +1,27 @@
+# Prettier Ignore File
+
+## contains broken JSON for tests
+
 test-resources
+
+## dist and build folders
+
 dist
-__tests__
-plugins
-product/target
-java/
+target
+site
 docs/
-tests/
-utility/
-package-lock.json
-package.json
 build
-.markdownlint.json
 docma-template
 node_modules
 coverage
+
+## IDEs configs and Java projects
+
+.vscode
+java/
+
+## Actually prettier is used only for JSON files, so other files are ignored
+
 *.js
 *.jsx
 *.md
@@ -23,4 +31,3 @@ coverage
 *.yml
 *.hbs
 *.yaml
-font-awesome.json
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,5 +1,12 @@
 # Change Log

+## [2025.01.00](https://github.com/geosolutions-it/MapStore2/tree/v2025.01.00) (2025-6-18)
+
+- **[Full Changelog](https://github.com/geosolutions-it/MapStore2/compare/v2024.02.02...v2025.01.00)**
+- **[Implemented enhancements](https://github.com/geosolutions-it/MapStore2/issues?q=is%3Aissue+milestone%3A%222025.01.00%22+is%3Aclosed+label%3Aenhancement)**
+- **[Fixed bugs](https://github.com/geosolutions-it/MapStore2/issues?q=is%3Aissue+milestone%3A%222025.01.00%22+is%3Aclosed+label%3Abug)**
+- **[Closed issues](https://github.com/geosolutions-it/MapStore2/issues?q=is%3Aissue+milestone%3A%222025.01.00%22+is%3Aclosed)**
+
 ## [2024.02.02](https://github.com/geosolutions-it/MapStore2/tree/v2024.02.02) (2024-12-11)

 - **[Full Changelog](https://github.com/geosolutions-it/MapStore2/compare/v2024.02.01...v2024.02.02)**

diff --git a/binary/bin-war/pom.xml b/binary/bin-war/pom.xml
@@ -3,13 +3,13 @@
    <groupId>it.geosolutions.mapstore</groupId>
    <artifactId>mapstore-bin-war</artifactId>
    <packaging>war</packaging>
-    <version>1.10-SNAPSHOT</version>
+    <version>1.9.0</version>
    <name>MapStore 2 Release Module WAR</name>
    <description>Creates the war for the binary package, adding customization (e.g. h2 database)</description>
    <url>http://www.geo-solutions.it</url>
    <properties>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
-        <tomcat.version>9.0.90</tomcat.version>
+        <tomcat.version>9.0.99</tomcat.version>
        <binary.number>${mapstore2.version}</binary.number>
    </properties>

@@ -31,6 +31,17 @@
                <artifactId>maven-war-plugin</artifactId>
                <version>3.4.0</version>
                <configuration>
+                    <packagingExcludes>
+                        WEB-INF/lib/*spring*5.3.18*.jar,
+                        WEB-INF/lib/json-lib-2.4-jdk15.jar,
+                        WEB-INF/lib/msg-simple-1.1.jar,
+                        WEB-INF/lib/btf-1.2.jar,
+                        WEB-INF/lib/commons-io-2.1.jar,
+                        WEB-INF/lib/commons-beanutils-1.8.0.jar,
+                        WEB-INF/lib/commons-logging-1.1.1.jar,
+                        WEB-INF/lib/jackson-coreutils-1.6.jar,
+                        WEB-INF/lib/stax-ex-1.8.jar
+                    </packagingExcludes>
                    <overlays>
                        <overlay>
                            <groupId>it.geosolutions.mapstore</groupId>

diff --git a/binary/pom.xml b/binary/pom.xml
@@ -3,7 +3,7 @@
    <parent>
        <groupId>it.geosolutions.mapstore</groupId>
        <artifactId>mapstore-root</artifactId>
-        <version>1.10-SNAPSHOT</version>
+        <version>1.9.0</version>
    </parent>
    <groupId>it.geosolutions.mapstore</groupId>
    <artifactId>mapstore-binary</artifactId>

diff --git a/build/docma-config.json b/build/docma-config.json
@@ -174,7 +174,6 @@
                "web/client/actions/fullscreen.js",
                "web/client/actions/maplayout.js",
                "web/client/actions/map.js",
-                "web/client/actions/maps.js",
                "web/client/actions/maptype.js",
                "web/client/actions/notifications.js",
                "web/client/actions/search.js",
@@ -189,7 +188,6 @@
                "web/client/reducers/controls.js",
                "web/client/reducers/featuregrid.js",
                "web/client/reducers/mapInfo.js",
-                "web/client/reducers/maps.js",
                "web/client/reducers/maptype.js",
                "web/client/reducers/notifications.js",
                "web/client/reducers/search.js",
@@ -242,7 +240,6 @@
                "web/client/plugins/ContextExport.jsx",
                "web/client/plugins/ContextImport.jsx",
                "web/client/plugins/Cookie.jsx",
-                "web/client/plugins/CreateNewMap.jsx",
                "web/client/plugins/Dashboard.jsx",
                "web/client/plugins/DashboardEditor.jsx",
                "web/client/plugins/Details.jsx",
@@ -275,7 +272,6 @@
                "web/client/plugins/MapFooter.jsx",
                "web/client/plugins/MapImport.jsx",
                "web/client/plugins/MapLoading.jsx",
-                "web/client/plugins/MapSearch.jsx",
                "web/client/plugins/MapTemplates.jsx",
                "web/client/plugins/MapViews.jsx",
                "web/client/plugins/Measure.jsx",
@@ -295,13 +291,16 @@
                "web/client/plugins/ResourcesCatalog/EditContext.jsx",
                "web/client/plugins/ResourcesCatalog/Favorites.jsx",
                "web/client/plugins/ResourcesCatalog/Footer.jsx",
+                "web/client/plugins/ResourcesCatalog/GroupManager.jsx",
                "web/client/plugins/ResourcesCatalog/HomeDescription.jsx",
                "web/client/plugins/ResourcesCatalog/ResourceDetails.jsx",
                "web/client/plugins/ResourcesCatalog/ResourcesFiltersForm.jsx",
                "web/client/plugins/ResourcesCatalog/ResourcesGrid.jsx",
+                "web/client/plugins/ResourcesCatalog/ResourcesSearch.jsx",
                "web/client/plugins/ResourcesCatalog/Save.jsx",
                "web/client/plugins/ResourcesCatalog/SaveAs.jsx",
                "web/client/plugins/ResourcesCatalog/TagsManager.jsx",
+                "web/client/plugins/ResourcesCatalog/UserManager.jsx",
                "web/client/plugins/RulesDataGrid.jsx",
                "web/client/plugins/RulesEditor.jsx",
                "web/client/plugins/RulesManagerFooter.jsx",
@@ -334,10 +333,8 @@
                "web/client/plugins/containers/ToolsContainer.jsx",
                "web/client/plugins/featuregrid/FeatureEditor.jsx",
                "web/client/plugins/index.jsdoc",
-                "web/client/plugins/manager/GroupManager.jsx",
                "web/client/plugins/manager/Manager.jsx",
                "web/client/plugins/manager/ManagerMenu.jsx",
-                "web/client/plugins/manager/UserManager.jsx",
                "web/client/plugins/print/Graticule.jsx",
                "web/client/plugins/print/OutputFormat.jsx",
                "web/client/plugins/print/Projection.jsx",

diff --git a/createProject.js b/createProject.js
@@ -83,7 +83,7 @@ function doWork(params) {
        })
        .then(() => {
            process.stdout.write('package.json file created\n');
-            return project.copyStaticFiles(projectFolder + '/static', params.outFolder, options, ['.editorconfig', 'LICENSE.txt', 'Dockerfile']);
+            return project.copyStaticFiles(projectFolder + '/static', params.outFolder, options, ['.editorconfig', 'LICENSE.txt']);
        })
        .then(() => {
            process.stdout.write('copied static files\n');

diff --git a/docs/developer-guide/integrations/geoserver.md b/docs/developer-guide/integrations/geoserver.md
@@ -45,6 +45,9 @@ This solution partially degradates the functionalities of user management UI of
 This example will focus on **PostgreSQL** database type
 I am assuming this is a new installation, so no existing user or map will be preserved

+!!! Warning
+    If you make a mistake in the above procedures and log out, you may not be able to log in again or you may lose your administrator rights. For this reason, it is recommended that you make a backup of your GeoServer data directory before starting the setup. If you encounter any problems, you can restore the backup and start over.
+
 ## Database preparation

 1. Follow [Geostore wiki](https://github.com/geosolutions-it/geostore/wiki/Building-instructions#building-geostore-with-postgres-support) to setup a postgresql database (ignore the geostore_test part)
@@ -103,6 +106,7 @@ Steps below reference user, group and role service configuration files, as neede
 - go Again in JDBC Role Service `geostore`
 - select Administrator role to `ADMIN`
 - select Group Administrator Role to `ADMIN`
+- click on "Save" button again

 ### Use these services as default


diff --git a/docs/developer-guide/integrations/users/ldap.md b/docs/developer-guide/integrations/users/ldap.md
@@ -15,7 +15,7 @@ If this causes confusion, you can disable the UI when using LDAP by removing the
 The LDAP storage can be configured in two ways:

 * *Synchronized* mode
-* *Direct connection* mode (experimental)
+* *Direct connection* mode

 ### Synchronized mode

@@ -25,8 +25,6 @@ Any other operation, for example getting user permissions on maps, always uses t

 Synchronized mode is faster for normal use, but data may dis-align when users are removed from the LDAP repository.

-In general we suggest to use synchronized mode, since it is the most stable and tested one.
-
 ```mermaid
 sequenceDiagram
    actor User
@@ -41,7 +39,7 @@ sequenceDiagram
    MapStore-->>User: Login successful
 ```

-### Direct connection mode (experimental)
+### Direct connection mode

 In direct connection mode, user data is always read from LDAP, for any operation, so there is no risk of misaligned data.


diff --git a/docs/developer-guide/local-config.md b/docs/developer-guide/local-config.md
@@ -73,9 +73,7 @@ This is the main structure:
      // Use POST requests for each WMS length URL highter than this value.
      "maxURLLength": 5000,
      // Custom path to home page
-      "homePath": '/home',
-      // If true it enables interactive legend for GeoServer WMS, WFS layers
-      "experimentalInteractiveLegend": true
+      "homePath": '/home'
  },
  // optional state initializer (it will override the one defined in appConfig.js)
  "initialState": {