Manage artifacts used by us and other Quarkus Platform participants

[ppalaga]

Fix #26068
Fix #26071
Fix #26072
Fix #26073
Fix #26087

[ppalaga]

See also https://issues.redhat.com/browse/QUARKUS-2213

A backport to 2.7 would be nice

[ppalaga]

907de33:

• Rebased
• Added the missing javassist constraint

[ppalaga]

a30d892:

• Ban javassist instead of managing it.

[ppalaga]

Is this good to merge now, @gastaldi @gsmet ?

[geoand]

The title of the PR looks misleading based on the number of changes of changes it introduces

[ppalaga]

The title of the PR looks misleading based on the number of changes of changes it introduces

Renamed

[gsmet]

Looks good overall but let's get another CI run to be on the safe side.

[gsmet]

I triggered a new CI run.

[ppalaga]

@gsmet Do I need to investigate the failing tests?

[gsmet]

@ppalaga could you have a look at @gastaldi 's question? Let's see what CI says once it's rebased.
The failures look odd but it might be an infrastructure flake.

[ppalaga]

@ppalaga could you have a look at @gastaldi 's question?

83688f6:

• Rebased
• Added

<dependency>
                <groupId>com.sun.mail</groupId>
                <artifactId>jakarta.mail</artifactId>
                <version>${jakarta.mail.version}</version>
            </dependency>

[gsmet]

Thanks!

[gsmet]

@ppalaga do you think this is still needed for the next 2.7?
@harshmadhani could you check if it's going to be a problem for prod? It might not be as it probably just points to the version we are currently using but let's make sure it doesn't cause you headaches.

[harshmadhani]

@gsmet Yes, since there is no change in versions, it should okay for prod. Thanks !

[ppalaga]

@ppalaga do you think this is still needed for the next 2.7?

No, in 2.7 we have some workarounds in place that are fine to live with till its EOL

[gsmet]

Thanks, let's not backport it then.