[MAGNOLIA-1990] Mg 3.5.2 Instance does not start if a Mg 3.0 module is added Created: 06/Jan/08  Updated: 02/Mar/11  Resolved: 02/Mar/11

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.5.2
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Giancarlo Berner Assignee: Philipp Bärfuss
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Mac OS X, Magnolia 3.5.2 EE, Tomcat 5.5


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)
Date of First Response:

 Description   

By accident I added a module created for Magnolia 3.0.5 to the /WEB-INF/lib of a Magnolia 3.5.2 author-instance.

When starting Magnolia, the author instance did not startup because the module used a 3.0 dependency (admin interface). The error:

ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/magnoliaAuthor] StandardContext.java(listenerStart:3768) 05.01.2008 21:02:23 Exception sending context initialized event to listener instance of class info.magnolia.cms.servlets.MgnlServletContextListener
java.lang.RuntimeException: info.magnolia.module.model.reader.ModuleDependencyException: Module XumaK : Components-module (version 1.1.0) is dependent on adminInterface version 3.0, but Magnolia Admin Interface Module (version 3.5.2) is currently installed.
at info.magnolia.cms.servlets.MgnlServletContextListener.contextInitialized(MgnlServletContextListener.java:200)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3764)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4216)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544)

Is it possible to still continue the instance's startup process and just ignore the module?



 Comments   
Comment by Magnolia International [ 02/Mar/11 ]

No it's not possible to ignore module dependency problems (we could, though, but such problems are likely to cascade to other modules, resulting in an incomplete startup).

Modules can declare dependencies leniently, by not specifying a version-dependency at all, or "opening" it (i.e depend on <version>3.0/*</version>, which translates to "3.0 or anything after that")

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