Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade Spring Context Support to Jakarta EE's com.sun.mail:jakarta.mail and com.sun.activation:jakarta.activation [SPR-17561] #22093

Open
spring-issuemaster opened this issue Dec 4, 2018 · 2 comments

Comments

@spring-issuemaster
Copy link
Collaborator

@spring-issuemaster spring-issuemaster commented Dec 4, 2018

Juergen Zimmermann opened SPR-17561 and commented

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.


Affects: 5.1.3

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

@spring-issuemaster spring-issuemaster commented Dec 4, 2018

Juergen Hoeller commented

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.

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

@spring-issuemaster spring-issuemaster commented Dec 4, 2018

Juergen Zimmermann commented

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.