[MGNLREST-355] Migrate to jakarta.annotation-api Created: 29/Mar/22  Updated: 23/Oct/23  Resolved: 30/Aug/22

Status: Closed
Project: Magnolia REST Framework
Component/s: None
Affects Version/s: 2.2.14
Fix Version/s: 3.0.0, 2.2.15

Type: Bug Priority: Neutral
Reporter: Michiel Meeuwissen Assignee: Chuong Doan Huy
Resolution: Fixed Votes: 0
Labels: quickwin
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: 3d 1.5h Time Spent: 3d 1.5h
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLREST-450 Multiple activation jars. Closed
is related to BUILD-871 Manage jakarta.activation dependencies Open
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLREST-478 Implement Sub-task Completed Chuong Doan Huy  
MGNLREST-479 Review code Sub-task Completed Mikaël Geljić  
MGNLREST-480 Pre-int QA Sub-task Closed Dai Ha  
MGNLREST-481 Final QA Sub-task Completed Jaroslav Simak  
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)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Epic Link: Headless Phase 2
Sprint: DevX 17
Story Points: 3
Team: DeveloperX

 Description   

info.magnolia.rest:magnolia-rest-content-delivery is depending on javax.annotation:javax.annotation-api.

I think this ought to be migrated to jakarta.annotation:jakarta.annotation-api which is iirc the successor and already used by e.g. apache-tika, which itself is a dependency of magnolia-core.

Notes
It seems jakarta.activation is replacing javax.activation. See https://newbedev.com/what-is-the-replacement-for-javax-activation-package-in-java-9



 Comments   
Comment by Richard Gange [ 15/Sep/22 ]

Hello mihxil-

This issue was fixed in version 6.2.23 of Magnolia.

Cheers
Rich

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