[MGNLPN-188] Personalization integration needs STK for license checking but has no dependency to it Created: 19/Sep/14  Updated: 11/Mar/21  Resolved: 11/Mar/21

Status: Closed
Project: Magnolia Personalization
Component/s: Integration
Affects Version/s: 1.0.1
Fix Version/s: 1.1.x

Type: Bug Priority: Neutral
Reporter: Natascha Desmarais Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: license, personalization-integration, stk
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnolia 5.3.3 - Personalization 1.0.1


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

 Description   

Right now it is possible to create an EEPro project without STK that installs everything around personalization, but the module personalization-integration cannot be started because it relies on the existence of info.magnolia.module.templatingkit.badge.LicenseChecker for the check for a valid EEPro license.

2014-09-19 12:01:07,927 ERROR info.magnolia.module.ModuleManagerImpl            : Can't start module personalization-integration
java.lang.NoClassDefFoundError: info/magnolia/module/templatingkit/badge/LicenseChecker

Either this module needs a modular dependency to the STK or even better, the LicenseChecker class should be made available around the core, or very basic modules.


Generated at Mon Feb 12 06:35:10 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.