[MGNLIMG-242] Support webp images also on aarch64 Created: 02/Aug/22 Updated: 20/Dec/22 Resolved: 22/Nov/22 |
|
| Status: | Closed |
| Project: | Imaging |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.0, 3.5.6 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Raphael Falvo | Assignee: | Oanh Thai Hoang |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | 0d | Remaining Estimate: | 0d |
| Σ Time Spent: | 1d 3h | Time Spent: | 1d 3h |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Attachments: |
|
||||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||||
| Sub-Tasks: |
|
||||||||||||||||||||||||||||||
| Template: | |||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||||
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||
| Epic Link: | Support | ||||||||||||||||||||||||||||||
| Sprint: | DevX 24 | ||||||||||||||||||||||||||||||
| Story Points: | 2 | ||||||||||||||||||||||||||||||
| Team: | |||||||||||||||||||||||||||||||
| 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> |
| Comments |
| Comment by Jan Haderka [ 17/Aug/22 ] |
|
Released under Apache 2.0 license, so all green on that side. |
| Comment by Jan Haderka [ 17/Aug/22 ] |
|
Also no existing CVE against it, so all green on that side too. |