#614: Update to 2023.01.xx

[dsuren1]

Description

This PR updates the MS submodule to latest 2023.01.xx as of this commit

Note:

• pom.xml doesn't have changes mentioned here and hence not modified

Things done:

• [x] #580 -> implemented, see this comment https://github.com/georchestra/mapstore2-georchestra/issues/580#issuecomment-1598913920
• [x] log4j update to log4j2
• [x] Database schema update (v.1.5.0-to-v2.0.0) - Implemented using update in schema validation, as done in MapStore.

Release notes update

Things to add to the release notest:

• The database of mapstore should automatically update creating the new tables. If the auto-update of the database do not work (e.g. some database permission issue in some custom installation) apply the migration script here as an alternative
• If you customized the the file log4j.properties in data directory, you have to replace it a new file, with
• A different name: log4j2.properties:
• A new syntax: here an example of the new syntax. See https://logging.apache.org/log4j/2.x/manual/migration.html for migration gudes.

  
  rootLogger.level = INFO
  appenders= console, file

appender.console.type = Console appender.console.name = LogToConsole appender.console.layout.type = PatternLayout appender.console.layout.pattern = %p %d{yyyy-MM-dd HH:mm:ss.SSS} %c::%M:%L - %m%n rootLogger.appenderRef.stdout.ref = LogToConsole rootLogger.appenderRef.console.ref = LogToConsole

appender.file.type = File appender.file.name = LogToFile2 appender.file.fileName=${sys:catalina.base}/logs/mapstore.log appender.file.layout.type=PatternLayout appender.file.layout.pattern=%p %d{yyyy-MM-dd HH:mm:ss.SSS} %C{1}.%M() - %m %n rootLogger.appenderRef.file.ref = LogToFile2

logger.restsrv.name=it.geosolutions.geostore.services.rest logger.restsrv.level= INFO logger.hibernate1.name=org.hibernate logger.hibernate1.level=INFO logger.trg1.name=com.trg logger.trg1.level=INFO

[tdipisa]

@offtherailz

Please evaluate why this is present and how to workaround it.

We know that, I've already mentioned that and it is also reported in description. The issue #580 will handle it. You have to only evaluate the other parts in this PR. If they are ok please put a comment informing about that. Did you review the rest?

For schema update, we may evaluate to ask to use

This is something to report in the final release notes. Maybe we can open an issue to collect involved things to avoid to miss something.

[offtherailz]

What about pom needed changes indicated here?

They should not be needed. They may be included if some customization that use logging was present in web/backend. This is not the case.