Jakarta - EE 10 - Move to the Angus Jakarta Mail implementation

[gsmet]

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:

• https://search.maven.org/artifact/org.eclipse.angus/angus-mail/1.0.0/jar that is just the implementation
• https://search.maven.org/artifact/org.eclipse.angus/jakarta.mail/1.0.0/jar that contains both the implementation and the API

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.

[quarkus-bot[bot]]

/cc @cescoffier

[gsmet]

We only it for tests so we will update it when subethasmtp moves to it.

[ppalaga]

@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.

[gastaldi]

After our latest meeting, the idea is to have a quarkus-angus extension in Quarkiverse

[ppalaga]

@gastaldi would you please create a qverse repo for angus mail?

[gsmet]

I'm not sure if having quarkus-angus makes sense. They live in different projects even if they share the same prefix. So probably better to create a quarkus-angus-mail extension.

[ppalaga]

@gastaldi I see that the repo exists, but it is empty. Your magic provisioning templates are still to be run?

[gastaldi]

You can use quarkus create extension angus-mail to create the skeleton

[gsmet]

Please don't close my issue, it has nothing to do with the availability of the extension :).

[gsmet]

You can use quarkus create extension angus-mail to create the skeleton

I think you need to specify the groupId to create a Quarkiverse one?

[gastaldi]

@gsmet no need to. The default is already io.quarkiverse.<PROJECT.NAME>

[gastaldi]

Hm, it generates the groupId as <groupId>io.quarkiverse.angus-mail</groupId>, but I guess it should be io.quarkiverse.angus.mail? WDYT

[gsmet]

It should either be angusmail or angus.mail if we want to stay consistent with the rest of the extensions.

The dot would make sense if we expect several angus extensions and that might be the case but in general we decided to go with io.quarkiverse.githubapp:quarkus-github-app for instance. Not all the extensions are consistent but most follow this pattern.

[maxandersen]

issue for angus mail extension is here: https://github.com/quarkusio/quarkus/issues/31285

[rsvoboda]

https://github.com/quarkiverse/quarkus-angus-mail repo is empty.

What are the plans with Angus / Jakarta Mail 2.1?

[gastaldi]

It's still in @ppalaga's TODO list. See https://quarkusio.zulipchat.com/#narrow/stream/187038-dev/topic/Quarkiverse.20Angus.20Mail