[MGNLRSSAGG-201] Module Magnolia RSS Aggregator Module (version 2.4.0) is dependent on mte (version 0.5/*), which was not found. Created: 10/Jul/15  Updated: 24/May/16  Resolved: 24/May/16

Status: Closed
Project: Magnolia RSS Aggregator Module
Component/s: None
Affects Version/s: 2.4
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Nils Breunese Assignee: Unassigned
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:
Visible to:
Rico Jansen

 Description   

The Magnolia module descriptor of magnolia-module-rssaggregator-2.4 has this dependency:

<dependency>
  <name>mte</name>
  <version>0.5/*</version>
</dependency>

However, pom.xml doesn't depend on mte, so unless we manually add a dependency on mte to our project we get this error message on Magnolia startup:

Module Magnolia RSS Aggregator Module (version 2.4.0) is dependent on mte (version 0.5/*), which was not found.


 Comments   
Comment by Richard Gange [ 24/May/16 ]

Hi Nils-

The pom only needs the dependency if there is a Java code dependency. In this case there is a dependency on resources provided by MTE. So the dependency is valid.

HTH
Rich

Comment by Nils Breunese [ 24/May/16 ]

I understand that technically a dependency on MTE in pom.xml is not necessary for the build of the module, but since MTE is needed to use the RSS Aggregator module at runtime, it would be handy if MTE was automatically included in your project when you add the RSS Aggregator module. Now we added the Aggregator module, started Magnolia, found that it wouldn't start up without MTE and had to manually add a dependency on MTE to our pom.xml.

Comment by Richard Gange [ 24/May/16 ]

Ok, I understand your point as well. I've seen this issue before as well in other areas. It helps if you include one of the poms from info.magnolia.eebundle for EE projects. This way you get a lot of the popular modules used in EE projects, such as, MTE. Otherwise, yes, at times you will hit problems like this one. So you will need to explicitly add the dependency to a custom pom.

Generated at Mon Feb 12 07:06:34 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.