feat: ensure maven 3.9

[spolti]

Motivation

Modifications

Result

[adambkaplan]

ubi10 upgrades the default to Maven 3.9: https://gitlab.com/redhat/centos-stream/rpms/maven/-/blob/c10s/maven.spec?ref_type=heads#L9

[terrytangyuan]

Could you update the PR description and address the comment from Adam?

[spolti]

For now, I think it is better to stay with UBI9, while trying UBI10 a few issues were found, including:

The Maven's ASM dependency is unbundled and missing

RHEL 10's sisu RPM (used by Maven for dependency injection) unbundles objectweb-asm, but the objectweb-asm RPM is not available in any UBI 10 repo (base, appstream, or CRB).
Symptom:

NoClassDefFoundError: org/objectweb/asm/ClassVisitor                                                                                                                                                                            

So Maven fails to inject any plugin compiled with Java 17+ bytecode (e.g., protobuf-maven-plugin v5.0.0).

Root cause: The package exists in CentOS Stream 10 AppStream (objectweb-asm-9.6-6.el10.noarch) but is not shipped in the UBI subset.

This is effectively a packaging bug — Maven is broken out of the box on UBI 10 for any plugin requiring bytecode scanning.

[adambkaplan]

This is effectively a packaging bug — Maven is broken out of the box on UBI 10 for any plugin requiring bytecode scanning.

Submitted this to RHEL for further investigation: https://issues.redhat.com/browse/RHEL-154034

[spolti]

@adambkaplan @terrytangyuan can we go with ubi9 for now?

[terrytangyuan]

Yes

[mkoncek]

The Maven's ASM dependency is unbundled and missing

It is bundled but the bytecode-version-handling code not been kept up-to-date.