| [angus-dev] Issue with META-INF/services/jakarta.mail.Provider |
Hi everyone, I’ve just recently subscribed to this mailing list, because we have a problem with the Eclipse Angus library, and I wanted to ask your opinion if this is an issue with the library or with our expectations. We have implemented a plugin for Atlassian Confluence that registers as the SMTP provider in order to get hold of outgoing email, because our plugin has to encrypt them. We used to do this by specifying our provider in META-INF/service/jakarta.mail.Provider within our jar, so it would be picked up and used as the default provider. This used to work well with com.sun.mail_jakarta.mail-1.6.7.jar, but not any more since Atlassian has upgraded to using org.eclipse.angus_angus-mail-2.0.3.jar. Strange enough, it may work or not, depending on the names of the two jars. So we assume it depends on the order in which they are loaded, and thus, which of the providers is found first or last in META-INF/services/jakarta.mail.Provider of the respective jar. However, we think that this indeterministic behavior that should not occur, should it? When we delete the META-INF/services/jakarta.mail.Provider in the org.eclipse.angus_angus-mail-2.0.3.jar, everything works as before. I’ve filed an issue at https://github.com/eclipse-ee4j/angus-mail/issues/170, because it looks like a bug to us, or perhaps like a regression of a similar issue that was introduced in javax.mail 1.6.2 and gave us the same symptoms. I wonder if you are saying that our approach is perhaps not supported or not the intended use, and we should do it differently? Thanks Metin |