[BLOSSOM-105] magnolia-module-blossom-extension-data:2.0.2 not compatible with Magnolia 4.5.8 Created: 26/Mar/13  Updated: 07/Nov/14  Resolved: 08/Apr/13

Status: Closed
Project: Blossom
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Tomas Brimor Assignee: Tobias Mattsson
Resolution: Not an issue 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   
 2013-03-26 10:10:51,553 ERROR info.magnolia.init.MagnoliaServletContextListener : Oops, Magnolia could not be started
info.magnolia.module.model.reader.ModuleDependencyException: Module Magnolia Standard Templating Kit Module (version 2.0.9) is dependent on data version 1.7.4/*, but Magnolia Data Module (version 1.7.3) is currently installed.
    at info.magnolia.module.model.reader.DependencyCheckerImpl.checkSpecificDependency(DependencyCheckerImpl.java:104)
    at info.magnolia.module.model.reader.DependencyCheckerImpl.checkDependencies(DependencyCheckerImpl.java:60)
    at info.magnolia.module.ModuleManagerImpl.loadDefinitions(ModuleManagerImpl.java:150)
    at info.magnolia.init.MagnoliaServletContextListener.contextInitialized(MagnoliaServletContextListener.java:153)
    at info.magnolia.init.MagnoliaServletContextListener.contextInitialized(MagnoliaServletContextListener.java:126)
[INFO] +- info.magnolia:magnolia-module-blossom-extension-data:jar:2.0.2:compile
[INFO] |  \- info.magnolia:magnolia-module-data:jar:1.7.3:compile


 Comments   
Comment by Tobias Mattsson [ 08/Apr/13 ]

Hello Tomas,

This is caused by mavens dependency mediation for transitive dependencies, the mechanism is documented at http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html

It works like this, if you have dependencies as follows:
your-webapp -> blossom-module-extension-data:2.0.2 -> module-data:1.7.3
your-webapp -> module-stk:2.0.9 -> module-data:1.7.4

Then maven will pick 1.7.3 because its the first appearance of this dependency on depth 3.

You can solve this by either rearranging your dependencies or add an explicit dependency on module-data in your pom file.

// Tobias

Generated at Sun Feb 11 23:30:10 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.