-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project update to the latest MapStore 2024.02 #714
Comments
* Update ms to latest * version updated * pom updated * workflow update * add missing theme variables * fix build * ms service to stable * snapshot repo removed * config updated * Fixed dependencies * Fixed missing file copy * Update pom.xml * Use mapstore services 1.8-SNAPSHOT --------- Co-authored-by: Lorenzo Natali <[email protected]>
@dsuren1 From functional tests performed it seems you have missed to add/consider the following in default config:
Can you please raise a PR to provide what is missing? Thank you so much. |
to the ones trying the upgrade path to 2024.02, some notes:
so i followed https://docs.mapstore.geosolutionsgroup.com/en/latest/developer-guide/mapstore-migration-guide/#database-update, but had to manually adapt some bits
with that done the db schema is updated, requests to the backend now succeed, and i see maps in the map loader/on maybe |
Description
It is requested to update the project to the latest MapStore version. The MapStore revision need to be updated to the latest stable branch 2024.02.xx.
Checks
It is necessary to check if the existing customizations are properly working after the project update. Custom specific extensions that are involved as part of this update work are the following. These will be tested separately for:
Notes
The project need to be updated by following the official migration guidelines involved.
In particular in the master branch
Preliminary checks and tests for this update will be performed on https://georchestra.geo-solutions.it/
Release procedures to follow are reported in project README.
The text was updated successfully, but these errors were encountered: