Benny Bottema

Yes, there are quite a few ways to approach this. Current workaround / canonical approach is to implement the exceptionHandler of a sent email: ```java // for async emails (sync...

The non-api jars have exactly the same classes in it so in runtime this should be fine. I'm wondering why smime-module relies on the -api version, though. Can't remember that...

Ok so bouncy castle pulls it in, as you said. I've tested ands verified the following doesn't pose any problems: ```xml jakarta.mail jakarta.mail-api jakarta.activation jakarta.activation-api ``` Would this solve your...

Uhm, modularity is a little beyond my knowledge currently, but I have done some module-related work on the upcoming 6.0.0 release in the develop branch. I'm close to releasing it,...

Ok, so multireleases is something mostly useful for the library maintainers: they can leverage JDK functions that are not available in earlier JDKs and then release multiple versions of a...

I'm still not clear on the issue here. What problem are we solving? Why are you unable to use the library as-is? Newer JDK's should be backwards compatible with legacy...

@lanthale, you are focusing on the solution, while I'm still trying to understand the problem (or rather I fail to see a problem to begin with). So if you could...

> I tried to commit but had no right to commit and therefor as attachment the files. You can commit on a fork of this repo and then file a...

I just merged a pull request that fixes the module names. I hope to work on the multirelease item now. One question, the requires/exports lines in module-info.java, is that manual...

To be honest I know next to nothing about OSGI and the only reason the headers you mention are there is because of pull request #146. So if you know...