[BUILD-950] Support webp images also on aarch64 Created: 17/Nov/22  Updated: 23/Oct/23  Resolved: 17/Nov/22

Status: Closed
Project: Build
Component/s: None
Affects Version/s: None
Fix Version/s: BOM 6.3.0, BOM 6.2.27

Type: Improvement Priority: Neutral
Reporter: Oanh Thai Hoang Assignee: Oanh Thai Hoang
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLIMG-242 Support webp images also on aarch64 Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
BUILD-951 Implementation Sub-task To Do  
BUILD-952 Review Sub-task To Do  
BUILD-953 Pre-Integration QA Sub-task To Do  
BUILD-954 QA Sub-task To Do  
Template:
Acceptance criteria:
Empty
Epic Link: DevX Bucket
Team: DeveloperX

 Description   

The current webp library used in the imaging module (sejda fork) is still not supporting aarch64 architecture. This makes m1 owner life a bit miserable when having to troubleshoot issues on modules using the webp format like dam focal.

usefulness fork has added m1 support. I tested it with dam focal on my machine and it seems to work well. The only issue is that if we define this library in dam focal module, the sejda one is still embedded from the imaging module making kind of collision, the only way to exclude the sejda one then is to add a dependency exclusion in the web app, which is not ideal.

Would it be possible to test that dependency ensuring there are no other issues with it and eventually switch to this new one ?

<dependency>
  <groupId>com.github.usefulness</groupId>
  <artifactId>webp-imageio</artifactId>
  <version>0.2.1</version>
</dependency> 

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