Depend on angus-mail, not jakarta.mail about greenmail HOT 2 OPEN

Angus org.eclipse.angus:angus-mail:2.0.1 also depends on jakarta.mail:jakarta.mail-api .

Jakarta.Mail is the essential interface and should be what you program (compile) against,
and Angus is one (of theoretically many) implementation(s) of jakarta.mail , and required at runtime.

So, transitively you always have the dependency on jakarta.mail ?

from greenmail.

Angus org.eclipse.angus:angus-mail:2.0.1 also depends on jakarta.mail:jakarta.mail-api .

That's not a problem because it depends on jakarta.mail-api. It doesn't bundle jakarta.mail-api.

Meanwhile, jakarta.mail bundles jakarta.mail-api. By "bundle" I mean that its jar file contains copies of all the classes from jakarta.mail-api.

Jakarta.Mail is the essential interface and should be what you program (compile) against,
and Angus is one (of theoretically many) implementation(s) of jakarta.mail , and required at runtime.

jakarta.mail:jakarta.mail-api is the interface. org.eclipse.angus:angus-mail is the implementation. Those are what Greenmail should depend on, as the Angus release notes say. "Most people will only need the main Angus Mail implementation in the angus-mail.jar and jakarta.mail-api.jar files together with the Angus Activation on the module path or on the class path."

org.eclipse.angus:jakarta.mail, which should not be used, is both of those jar files combined into a single jar file. Using it in combination with either of the others causes you to have multiple copies of those classes on your classpath.

from greenmail.