I don't know if the master branch is still in use for dev purposes (last commit 20 days ago, more recent work on the other branches it seems), but this is currently the branch which is responsible of the "latest" docker image, and for now, the produced artifact are broken, because of 2 different spring versions being in the classpath at the same time, leading to the following message:
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/mapstore]]
at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:440)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:726)
... 37 more
Caused by: java.lang.IllegalArgumentException: More than one fragment with the name [spring_web] was found. This is not legal with relative ordering. See section 8.2.2 2c of the Servlet specification for details. Consider using absolute ordering.
Note: the docker image is affected (and used in the official docker composition), but also the generated war which is attached to the github action.
I don't know if the master branch is still in use for dev purposes (last commit 20 days ago, more recent work on the other branches it seems), but this is currently the branch which is responsible of the "latest" docker image, and for now, the produced artifact are broken, because of 2 different spring versions being in the classpath at the same time, leading to the following message:
Note: the docker image is affected (and used in the official docker composition), but also the generated war which is attached to the github action.