[MAGNOLIA-4394] ModuleVersionHandlerTestCase doesn't properly support tests that require loading of module definitions Created: 26/Apr/12  Updated: 02/Aug/16  Resolved: 02/Aug/16

Status: Closed
Project: Magnolia
Component/s: testing
Affects Version/s: 4.5.2
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Daniel Lipp Assignee: Unassigned
Resolution: Outdated 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   

Due to the different classloder used by maven surefire plugin (does not allow us to iterate jars and their contained resources to find all module definition files that exist in the class path) bootstrap files might not be properly loaded when running tests on console.

The type info.magnolia.module.templatingkit.util.SureFireModuleManager addresses this problem but it's not yet usable together with ModuleVersionHandlerTestCase.



 Comments   
Comment by Daniel Lipp [ 27/Apr/12 ]

Be sure to re-activate WebdavModuleVersionHandlerTest#testFreshInstall which is only @ignored because of this bug (run's fine in IDE but not in console).

Comment by Michael Mühlebach [ 02/Aug/16 ]

Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
Given that the this issue has seen no attention for quite a while and belongs to an old version, we're not going to address this issue any more. Instead we will focus on issues with a higher impact and more votes.
Under the assumption this issue is no longer relevant, I'm going to close it to set expectations so the issue doesn't stay open for ages with no updates. If it is still relevant please feel free to open a new issue in the appropriate project.

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