Details
-
Improvement
-
Resolution: Outdated
-
Minor
-
None
-
3.5.2
-
None
-
Mac OS X, Magnolia 3.5.2 EE, Tomcat 5.5
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?