You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to 25.07.10_lts_v10 or 24.12.27_lts_v20, clicking the Bundles tab in the Publishing Queue portlet throws a JSP compilation error and the tab fails to load entirely:
Only a type can be imported. com.dotcms.repackage.com.google.common.base.CaseFormat resolves to a package
Root cause: Two changes landed in both LTS releases that were never coordinated:
The dot.guava artifact (com.dotcms.lib:dot.guava:11.0.1_2) was removed from the classpath as part of the fix(security): Upgrade vulnerable dependencies flagged by OWASP Dependency Check #35235 backport (commit 338cb6a5f1 on 25.07.10 LTS, 3f6b6e89a2 on 24.12.27 LTS). This artifact had previously provided com.dotcms.repackage.com.google.common.base.CaseFormat.
view_unpushed_bundles.jsp still has a stale <%@page import="com.dotcms.repackage.com.google.common.base.CaseFormat"%> at line 1 — an import that was harmless while dot.guava was on the classpath, but is now unresolvable.
The fix already exists on main (PR #35362, commit d373a563b9, April 17 2026) but was never backported to either LTS branch.
Steps to Reproduce
Upgrade to dotCMS 25.07.10_lts_v10 or 24.12.27_lts_v20
Navigate to the Publishing Queue portlet
Click the Bundles tab
Observe a 500 error / blank page; server logs show JSP compilation failure
Problem Statement
After upgrading to
25.07.10_lts_v10or24.12.27_lts_v20, clicking the Bundles tab in the Publishing Queue portlet throws a JSP compilation error and the tab fails to load entirely:Root cause: Two changes landed in both LTS releases that were never coordinated:
dot.guavaartifact (com.dotcms.lib:dot.guava:11.0.1_2) was removed from the classpath as part of the fix(security): Upgrade vulnerable dependencies flagged by OWASP Dependency Check #35235 backport (commit338cb6a5f1on 25.07.10 LTS,3f6b6e89a2on 24.12.27 LTS). This artifact had previously providedcom.dotcms.repackage.com.google.common.base.CaseFormat.view_unpushed_bundles.jspstill has a stale<%@page import="com.dotcms.repackage.com.google.common.base.CaseFormat"%>at line 1 — an import that was harmless whiledot.guavawas on the classpath, but is now unresolvable.The fix already exists on
main(PR #35362, commitd373a563b9, April 17 2026) but was never backported to either LTS branch.Steps to Reproduce
25.07.10_lts_v10or24.12.27_lts_v20Acceptance Criteria
<%@page import="com.dotcms.repackage.com.google.common.base.CaseFormat"%>fromview_unpushed_bundles.jspon both LTS branches (mirrors the fix in PR chore: remove unused imports from view_unpushed_bundles.jsp #35362)25.07.10_lts_v10and24.12.27_lts_v20dotCMS Version
25.07.10_lts_v1024.12.27_lts_v20Severity
High — Major functionality broken (Publishing Queue Bundles tab completely inaccessible after upgrade)
Links
https://dotcms.freshdesk.com/a/tickets/37546
https://dotcms.freshdesk.com/a/tickets/37554