[SPR-17561] Upgrade Spring Context Support to Jakarta EE's com.sun.mail:jakarta.mail and com.sun.activation:jakarta.activation Created: 04/Dec/18  Updated: 15/Jan/19

Status: Open
Project: Spring Framework
Component/s: Messaging
Affects Version/s: 5.1.3
Fix Version/s: 5.x Backlog

Type: Improvement Priority: Minor
Reporter: Juergen Zimmermann Assignee: Juergen Hoeller
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Days since last comment: 1 year, 30 weeks, 3 days ago
Last commented by a User: true
Last updater: Spring Issuemaster


Spring Context Support is using javax.mail:javax.mail-api and javax.activation:javax.activation-api. Meanwhile there is com.sun.mail:jakarta.mail and com.sun.activation:jakarta.activation.

Comment by Juergen Hoeller [ 04/Dec/18 ]

We generally compile against baseline APIs, not necessarily against the latest... except for cases where we need (optional) dependencies on newer interfaces, like with Servlet 4.0 where we compile against 4.0 while retaining 3.1 compatibility at runtime. From that perspective, I see us hanging on to the common EE 7/8 API artifacts as a baseline for the time being.

Is there a specific reason why you'd like us to switch to the Jakarta-provided artifacts? A concrete application project can bring in the Jakarta variant at runtime in any case since we are not enforcing the Oracle-provided artifacts, in particular not for optional dependencies, just using them for compilation purposes as the common reference APIs out there.

Comment by Juergen Zimmermann [ 04/Dec/18 ]

OK, got it. I thought that you are compiling against the latest API versions.

Comment by Spring Issuemaster [ 14/Jan/19 ]

The Spring Framework has migrated to GitHub Issues. Please visit spring-projects/spring-framework#22093 for further activity, or to subscribe to receive notifications.

Generated at Fri Aug 14 15:19:47 UTC 2020 using Jira 8.5.4#805004-sha1:0444eab799707f9ad7b248d69f858774aadfd250.