-
Notifications
You must be signed in to change notification settings - Fork 181
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
Cannot use Greenmail with Spring Boot 3 #512
Comments
@bodiam , try to exclude the transitive dependency on GreenMail depends on Jakarta Mail, which again brings along jakarta.activation implementation of Spring Boot 3 brings along jakarta.activation implementation of So you have to exclude one of them, to avoid conflict from having two implementations. Exclude either angus-activation ... <dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-mail</artifactId>
<exclusions>
<exclusion>
<groupId>org.eclipse.angus</groupId>
<artifactId>angus-activation</artifactId>
</exclusion>
</exclusions>
</dependency> ... or (old Jakarta Mail 2.x) com.sun.mail implementation: <dependency>
<groupId>com.icegreen</groupId>
<artifactId>greenmail-junit5</artifactId>
<version>2.0.0-alpha-3</version>
<scope>test</scope>
<exclusions>
<exclusion>
<groupId>com.sun.mail</groupId>
<artifactId>jakarta.mail</artifactId>
</exclusion>
</exclusions>
</dependency> For a Spring Boot 3 application, I'd recommend to exclude GreenMails Migrating GreenMail to Angus-Mail 2.1 is work-in-progress and planned for GreenMail 2.1 (version parity with Jakarta Mail 2.1). |
@marcelmay Thanks for the example and the explanation. I was under the impression that
|
Hi all,
I'm currently affected by this issue: spring-projects/spring-boot#33452
I also have this problem with Spring Boot 3 and Greenmail, but I'm using Greenmail Alpha 3, and the only dependency I have depending on
com.sun.activation:jakarta.activation:2.0.1
is Greenmail:Shouldn't Greenmail stop depending on this? (I thought that was the main reason to use Greenmail 2.0?)
The text was updated successfully, but these errors were encountered: