Hmm, except it requires Java 11... :-/

Yes, I noticed the impsort issue yesterday with GH Windows builds. I was wondering why dependabot didn't update the plugin, and I've found this: #338 :D

Our plan was to move to 11 with the Jakarta update, which is now done on Quarkus. I think it will be fine to mandate 11 from now on and only update parent in the Jakarta branches (or main if it is already Jakarta).

We do need to fix the Maven version in the build pipelines to be able to build the javax versions.

Hah, I looked for dependabot PR but didn't look far enough into the past :-)

Yeah I'm doing the same on Fault Tolerance: merging jakarta into main, which includes bumping to 11. So long, Java 8! :-)

To fix the Maven version in the CI:
smallrye/smallrye-config@6ddbf89

I think we should merge the Jakarta POM into the main one and drop it, meaning that instead of using smallrye-parent-jakarta, you use smallrye-parent again and bump Java to 11. This would mean the last parent version for the javax dependencies is 38. If we need further updates, we either have to do a x.y release or override the SR project directly. Effectively, everything that is javax should be in maintenance mode now, so I do not expect requiring bumping their parent versions.

@cescoffier
@sberyozkin
@aureamunoz
@jmartisk
@xstefank
@jponge
@brunobat
@MikeEdgar
@phillip-kruger
@ozangunalp

Does anyone have any concerns or restrictions?

I agree with removing the javax parent POM and keeping only the jakarta one (even though I use build-parent and manage dependencies myself :-) ).