fix: use correct mail dependencies

[buehner]

Description

This is a bugfix for the mail dependencies in succession of the spring 6 migration (sun vs jakarta packages).

Explanation:

The used parent pom spring-boot-dependencies (via spring-boot-starter-parent) declares a property jakarta-mail.version for the underlying jakarta.mail:jakarta.mail-api dependency. Within this project, this property has been "overwritten" and (mis-)used for the com.sun.mail:jakarta.mail dependency instead.

When using the mail functionality based on spring (JavaMailSender) this misconfiguration leads to an exception (could not find class...). The change of this PR fixes the issue.

Pull request type

• Bugfix
• Feature
• Dependency updates
• Tests
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe)

Do you introduce a breaking change?

• Yes
• No

Checklist

• I understand and agree that the changes in this PR will be licensed under the
  Apache Licence Version 2.0.
• I have followed the guidelines for contributing.
• The proposed change fits to the content of the code of conduct.
• I have added or updated tests and documentation, and the test suite passes (run mvn test locally).
• I have added a screenshot/screencast to illustrate the visual output of my update.

[KaiVolland]

Do the two dependencies have to co-exists or can one of them be removed/replaced by the other one? Looks a bit confusing to me.

[buehner]

Yes. They have to co-exist. Mailing will not work otherwise.

[dnlkoch]

Thanks!

[github-actions]

🎉 This issue has been resolved in version 20.3.1 🎉

The release is available on:

• v20.3.1
• GitHub release

Your semantic-release bot 📦🚀