[MGNLSCH-6] Initialization Exception raised on startup with Magnolia EE 3.5-rc3 Created: 23/Nov/07  Updated: 02/Dec/13  Resolved: 28/Nov/07

Status: Closed
Project: Scheduler
Component/s: None
Affects Version/s: 1.0-rc2
Fix Version/s: 1.1

Type: Bug Priority: Blocker
Reporter: Vivian Steller Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File scheduler-exception-on-startup-Magnolia-EE-3.5-rc3.txt    
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:

 Description   

After fresh install of Magnolia EE 3.5-rc3 (bundle) the startup of the scheduler module fails with the following exception (see full stack trace in file attached):

info.magnolia.cms.module.InitializationException: can't initialize module [scheduler]

Java Version is:
java version "1.5.0_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-164)
Java HotSpot(TM) Client VM (build 1.5.0_07-87, mixed mode, sharing)



 Comments   
Comment by Philipp Bracher [ 27/Nov/07 ]

The issue is that 1.0-rc2 was compiled against 3.0. 1.1 will be released compiled against 3.5.

This is only a problem because the former Content was a class but is now a interface.

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