...
This project has no J2EE/jakarta dependencies and so works with both the 10.x.y and 11.x.y versions of jetty - subject to the version of logback deployed being pinned (see below)
Check Changes
First, we need to track any changes in the origin\11 branch. Cherry pick in any appropriate changes.
...
| Code Block |
|---|
<logback.version>1.3.0-alpha16<5</logback.version> |
You must also override the version in start.d\idp-system.ini This allows and in the same jetty base to be deployed against Jetty 10 (which uses logback 1.3.x) and Jetty 11 (which uses logback 1.4.x)pom
| Note |
|---|
The Jetty 11 and Jetty 10 versions no longer interoperate so you need to make changes in the jetty11 and the jetty 10 branches. In practise this does not need to be revised unless there is a logback issue. |
SLF4J Version
Check the slf4j version in the top level pom for the jetty project and amend as appropriate
| Code Block |
|---|
<slf4j.version>2.0.5</slf4j.version> |
You should also override the version in start.d\idp-system.ini This is defensive against Jetty 10 and Jetty 11 versions drifting apart
The change must be made in the pom as well as the start.d\idp-system.ini
start.d/idp.ini
Any changes to this file may need to be reflected in changes to the file idp.ini.rewrite.property.names and/or idp.ini.windows and/or idp-system.windows
Properties new to
idp.inithat are occur inidp.ini.rewrite.property.namesshould be added toidp-system.iniif they are requiredProperties name changes must be added to
idp.ini.rewrite.property.names. Note that the name changes are cumulativeProperties new to
idp.inithat do not occur inidp.ini.rewrite.property.namesshould be added toidp.ini.windowsif they are required. Add them below the "don't change these values" lines.
...