[MSITEMESH-55] Dependency on personalization should not be optional Created: 27/Oct/17  Updated: 02/Mar/23

Status: Open
Project: SiteMesh
Component/s: None
Affects Version/s: 1.1.2
Fix Version/s: None

Type: Bug Priority: High
Reporter: Roman Kovařík Assignee: Unassigned
Resolution: Unresolved Votes: 2
Labels: maintenance, quickwin
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLCAMPU-76 Dependency on personalization in not ... Open
causality
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: Support
Team: DeveloperX

 Description   

Module declares dependency as optional although a p13n class is used in the version handler, resulting into:

Caused by: java.lang.NoClassDefFoundError: info/magnolia/advancedcache/personalization/cache/PersonalizedCacheKeyGenerator

when starting a webapp without p13n.



 Comments   
Comment by Mariusz Chruscielewski [ 13/Jul/19 ]

This bug is present in 6.1. Is there any workaround for that ?

Comment by Richard Gange [ 30/Apr/20 ]

It seems the workaround is one of two options:

  1. Exclude sitemesh.
  2. Include advance cache for personalization and personalization integration modules
Generated at Mon Feb 12 10:57:21 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.