[MAGNOLIA-2568] File extraction md5 check failures should be reported to the update mechanism's UI. to use the InstallContext log methods Created: 21/Jan/09  Updated: 23/Jan/13  Resolved: 26/Jan/09

Status: Closed
Project: Magnolia
Component/s: core, updatemechanism
Affects Version/s: 3.6.3
Fix Version/s: 4.0

Type: Bug Priority: Major
Reporter: Philipp Bärfuss Assignee: Magnolia International
Resolution: Fixed 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   

If a file extraction fails because of a failing MD5 check this is only logged (in terms of slf4j), but not shown in the UI.
We should allow the file extraction mechanism to use the InstallContext log methods.



 Comments   
Comment by Magnolia International [ 21/Jan/09 ]

Committed a solution which could be improved - maybe by abstracting the error/exception handling in what is not the FileExtractionLogger. Handling of IOException could be handled by this component too - where the implementation specific to the ModuleFilesExtraction task would then directly throw TaskExecutionException.

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