-
-
Notifications
You must be signed in to change notification settings - Fork 270
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
Update from javax.mail:1.6.0 to jakarta.mail:1.6.3 #213
Comments
I'm fine moving to Eclipse Jakarta Mail for the 5.x.y release as well if that solves your problem; I don't see any downsides to that (would result in release 5.2.0). |
I don't see a problem either (that's why I proposed it in the first place 😃) and it would be great to have it in a future release. |
I removed all the version nonsense as I had myself confused as well it seems. Note: as can be read on the official website, Jakarta Mail 1.6.3 contains the same as Javax Mail 1.6.2. I only need to analyse the impact of upgrading 1.6.0 to 1.6.2 then. (also relates to #184 and #186) /edit: impact seems limited, going ahead with the change... |
I just realized some of the dependencies also will need to be upgraded. |
Great 👍 sounds good. Waiting for a release with the new dependencies. |
I've released 5.2.0 which concludes the switch to Jakarta Mail. |
Perfect, thank you! |
Hi,
we want to use
simple-java-mail
internally within our company as well as in an Eclipse Foundation open source project. It works great for our purpose but unfortunately we need to be compliant with various policies. One of the dependencies of this project iscom.sun.mail:javax.mail
which is no longer supported from it's original repository and has moved to the Eclipse Foundation (https://github.com/eclipse-ee4j/javamail). Would it be an option to switch tocom.sun.mail:jakarta.mail:1.6.3
? A dependency from an unsupported project violates our policies. Having the Eclipse projects as a dependency would help us a lot.cc @eriksven @selobosi
The text was updated successfully, but these errors were encountered: