-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Jakarta - EE 10 - Move to the Angus Jakarta Mail implementation #26989
Comments
/cc @cescoffier |
We only it for tests so we will update it when subethasmtp moves to it. |
@gsmet what is the plan here actually? Are you planning to have an Angus Mail extension by any chance? I am looking for a place to consolidate the Angus mail code we have in Camel Quarkus and CXF. |
After our latest meeting, the idea is to have a |
@gastaldi would you please create a qverse repo for angus mail? |
I'm not sure if having |
You can use |
Please don't close my issue, it has nothing to do with the availability of the extension :). |
I think you need to specify the groupId to create a Quarkiverse one? |
@gsmet no need to. The default is already |
Hm, it generates the groupId as |
It should either be The dot would make sense if we expect several |
issue for angus mail extension is here: #31285 |
https://github.com/quarkiverse/quarkus-angus-mail repo is empty. What are the plans with Angus / Jakarta Mail 2.1? |
It's still in @ppalaga's TODO list. See https://quarkusio.zulipchat.com/#narrow/stream/187038-dev/topic/Quarkiverse.20Angus.20Mail |
What are the plans with angus? |
@ppalaga Any progress? |
I included This all works fine except in native mode as Angus Mail classes are not registered to be included in native image. I guess an official Quarkus extension would resolve that problem. Are there any work-arounds to get an implementation of jakarta mail included in native image? |
We have https://github.com/quarkiverse/quarkus-angus-mail but nothing was pushed to that repository yet. |
Also it's funny because |
@maxandersen @ppalaga I've pushed some code to https://github.com/quarkiverse/quarkus-angus-mail. I've tested native locally and it seems to work now. @steinsag, Can you please try cloning and building the extension locally and using it in your project? |
@gastaldi This looks very promising. I used the following classes to construct a raw MimeMessage with HTML and TXT body plus an attachement. I didn't send the email as I will hand over the raw message to AWS SES. But I think it works, because creating the initial
Do we need to register additional
as there is a transitive dependency towards |
Feel free to create issues there and submit PRs if needed |
So everything seems to be ready. What is needed now to get this officially released? |
I'll add some tests and release 0.0.1 afterwards |
Any chance to get it released today? Otherwise, I would need to create a private fork. |
/cc @gastaldi ^ |
Apparently, @gastaldi can read minds as I see a release is already in progress :). |
https://repo1.maven.org/maven2/io/quarkiverse/angusmail/quarkus-angus-mail/0.0.1/ is now released. Enjoy! |
@gsmet not sure if this issue is okay to be closed, so I'll leave it for you to decide |
...and live on production :-) Thank you very much @gastaldi for your support! |
For now, we are using the old implementation targeting EE 9.
EE 10 and Jakarta Mail 2.1 introduced a new implementation called Angus.
Note that there are 2 different artifacts:
We need to choose what's more practical for us but in general I would recommend to use the implementation that does NOT contain the API because otherwise we would have to add exclusions for all artifacts depending on the API.
The text was updated successfully, but these errors were encountered: