Skip to content

NotificationPortlet 4.8.3

Choose a tag to compare

View all tags
@bjagg bjagg released this 04 May 22:42
· 20 commits to master since this release
v4.8.3
6dfb8d6
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Patch release — single fix on top of v4.8.2.

Fix

The obsolete ch.qos.logback.classic.selector.servlet.ContextDetachingSCL listener has been removed from notification-portlet-webapp/src/main/webapp/WEB-INF/web.xml (PR #693). The class was part of Logback's J2EE selector machinery and was removed in Logback 1.3.x.

Today the listener still loads cleanly because NotificationPortlet bundles Logback 1.1.11 (pinned by Spring Boot 1.5.22, which is itself EOL since 2019). But every other portlet in the fleet that bumped Logback to 1.3+ during the 2026-05 fleet release wave hit ClassNotFoundException at context startup with this exact listener — and NotificationPortlet would hit the same wall the moment its Spring Boot or Logback is bumped.

The listener also has no functional value here. The original loggingSeparation guidance (the URL in the deleted comment) was for using LoggerContextSelector with hot-deploy of separate webapps, which is not how this portal's logging is set up.

Compatibility

  • Drop-in upgrade for any deployment running v4.8.2.
  • No dep changes, no schema changes, no API contract changes.
  • Java 11, Tomcat 8.5/9.x as before.

Out of scope

  • Full Logback / Spring Boot modernization is a separate, much larger effort. Spring Boot 1.5 ships Logback 1.1.x and slf4j 1.7.x; bumping just Logback in isolation breaks Boot's auto-config because the version is effectively pinned by the Spring Boot generation. The Spring Boot 1.5 → 2.7 (or alternative) migration is tracked outside this patch.
Assets 2
Loading