GH-40649: [CI][Release][Java] Use Maven 3.8 for verify-rc-source-java-linux-almalinux-8-amd64

[kou]

Rationale for this change

#39696 requires Maven 3.6 or later.

What changes are included in this PR?

Use Maven 3.8.

Are these changes tested?

Yes.

Are there any user-facing changes?

No.

• GitHub Issue: [CI][Release][Java] verify-rc-source-java-linux-almalinux-8-amd64 failed with old Maven #40649

[kou]

@github-actions crossbow submit verify-rc-source-java-linux-almalinux-8-amd64

[github-actions]

⚠️ GitHub issue #40649 has been automatically assigned in GitHub to PR creator.

[vibhatha]

=============================
Build and test Java libraries
=============================
/arrow/java /arrow /
/arrow/dev/release/verify-release-candidate.sh: line 614: mvn: command not found
Failed to verify release candidate. See /tmp/arrow-HEAD.FB64e for details.

[kou]

@github-actions crossbow submit verify-rc-source-java-linux-almalinux-8-amd64

[github-actions]

Revision: 3cbf8c0

Submitted crossbow builds: ursacomputing/crossbow @ actions-92e7ff8fc8

Task	Status
verify-rc-source-java-linux-almalinux-8-amd64

[vibhatha]

@kou this is a bit odd:https://github.com/ursacomputing/crossbow/actions/runs/8334984011/job/22809595263#step:6:53820
Should we re-run?

[kou]

Should we re-run?

Done!

[vibhatha]

@github-actions crossbow submit java

[github-actions]

Revision: 3cbf8c0

Submitted crossbow builds: ursacomputing/crossbow @ actions-9c4db745cb

Task	Status
java-jars
verify-rc-source-java-linux-almalinux-8-amd64
verify-rc-source-java-linux-conda-latest-amd64
verify-rc-source-java-linux-ubuntu-20.04-amd64
verify-rc-source-java-linux-ubuntu-22.04-amd64
verify-rc-source-java-macos-amd64

[vibhatha]

@github-actions crossbow submit verify-rc-source-java-linux-almalinux-8-amd64

[github-actions]

Revision: 3cbf8c0

Submitted crossbow builds: ursacomputing/crossbow @ actions-2f9781ecf4

Task	Status
verify-rc-source-java-linux-almalinux-8-amd64

[vibhatha]

@kou I think something is missing here. I am not quite sure what. Need to evaluate further.

[kou]

The error message:

https://github.com/ursacomputing/crossbow/actions/runs/8335526861/job/22811169947#step:6:52650

Error:  Error occurred during initialization of boot layer
Error:  java.lang.module.FindException: Module flatbuffers.java not found, required by org.apache.arrow.vector
Error:  Error occurred during initialization of boot layer
Error:  java.lang.module.FindException: Module flatbuffers.java not found, required by org.apache.arrow.vector

[kou]

Is flatbuffers.java an auto generated file?

[kou]

It's referred from

arrow/java/vector/src/main/java/module-info.java

Line 43 in 0956f3f

requires flatbuffers.java;

[kou]

@jduo Do you know what is the problem of #40650 (comment) ? Should we use different Maven version? (Maven 3.8 has a problem?)

[vibhatha]

@kou is there a way to locally test this using docker/archery to reproduce if possible?

[jduo]

It's referred from

arrow/java/vector/src/main/java/module-info.java

Line 43 in 0956f3f

requires flatbuffers.java;

flatbuffers.java is the automatically generated module name for flatbuffers-java.jar (rather than being an actual .java file).

[jduo]

@jduo Do you know what is the problem of #40650 (comment) ? Should we use different Maven version? (Maven 3.8 has a problem?)

When adding module support, I ran into issues with very specific versions of some plugins but don't remember the maven version itself being an issue. The ones that really caused problems were the maven-shade-plugin and the maven-analyze-plugin.

[kou]

is there a way to locally test this using docker/archery to reproduce if possible?

You can use archery docker run -e TEST_DEFAULT=0 TEST_JAVA=1 almalinux-verify-rc.

[kou]

@jduo Thanks for taking a look at this. Hmm... It seems that we need to look into this to fix this...

[kou]

AlmaLinux 8 ships Maven 3.8.5.
#40514 used Maven 3.8.7 via conda and it worked.

It seems that Maven 3.8.5 doesn't work.

I close this in favor of #40514. #40514 also uses newer Maven.