[MAGNOLIA-1700] API compatibility for modules broken (from 3.0 to 3.1) Created: 24/Aug/07  Updated: 29/Nov/07  Resolved: 29/Nov/07

Status: Closed
Project: Magnolia
Component/s: updatemechanism
Affects Version/s: 3.1 M3
Fix Version/s: 3.5 RC2

Type: Bug Priority: Major
Reporter: Oliver Lietz Assignee: Magnolia International
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   

running Magnolia update (trunk) breaks when using DMS module 1.1.1, this is also true for custom modules written against 3.0 api.

(You have to change adminInterface's dependency version from 3.0 to 3.1.0-SNAPSHOT in dms.xml to start Magnolia, otherwise another error will occur.)

[...]
WARN info.magnolia.cms.module.AbstractModule AbstractModule.java(<init>:75) 24.08.2007 14:49:24 This module extends the deprecated AbstractModule class [class info.magnolia.module.dms.DMSModule]
ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/magnolia].[default] StandardWrapperValve.java(invoke:253) 24.08.2007 14:49:24 Servlet.service() for servlet default threw exception
java.lang.IncompatibleClassChangeError
at info.magnolia.module.dms.DMSModule.configureMenu(DMSModule.java:72)
at info.magnolia.module.dms.DMSModule.onRegister(DMSModule.java:60)
at info.magnolia.cms.module.AbstractModule.register(AbstractModule.java:110)
at info.magnolia.module.LegacyModuleVersionHandler$1.execute(LegacyModuleVersionHandler.java:41)
at info.magnolia.module.ModuleManagerImpl.installOrUpdateModule(ModuleManagerImpl.java:391)
at info.magnolia.module.ModuleManagerImpl.performInstallOrUpdate(ModuleManagerImpl.java:190)
at info.magnolia.module.ModuleManagerUI.execute(ModuleManagerUI.java:54)
at info.magnolia.cms.filters.MagnoliaMainFilter.doFilter(MagnoliaMainFilter.java:80)
at info.magnolia.cms.filters.AbstractMagnoliaFilter.doFilter(AbstractMagnoliaFilter.java:46)
[...]



 Comments   
Comment by Magnolia International [ 29/Nov/07 ]

> You have to change adminInterface's dependency version from 3.0 to 3.1.0-SNAPSHOT in dms.xml to start Magnolia, otherwise another error will occur.

Well, that's the point of the dependency definition. dms-1.1.1 depends on admininterface 3.0, and that has to be read "dms can not work with any other version than admininterface 3.0".

To make custom modules work, you unfortunately will have to recompile them (no code changes), because a bunch of classes (HierarchyManager, Content, NodeData) have become interfaces.

Generated at Mon Feb 12 03:29:28 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.