[Bug] build-env-ldb-toolchain-latest ships Maven 3.6.3 but master FE requires Maven >= 3.9.0

[jonathanhu237]

Search before asking

• I had searched in the issues and found no similar issues.

Version

master branch
commit: bcfcef3

What's Wrong?

I encountered a build-environment mismatch when trying to build the latest Doris master branch with the recommended Docker image apache/doris:build-env-ldb-toolchain-latest.

The image currently provides Maven 3.6.3, but the current FE build requires Maven version [3.9.0,) according to fe/pom.xml.

Because of this mismatch, the build fails during the FE phase with the Maven enforcer version check error.

What You Expected?

I expected the recommended Docker image apache/doris:build-env-ldb-toolchain-latest to satisfy the current build requirements of the master branch, including the required Maven version, so that the FE build could proceed normally.

How to Reproduce?

1. Pull the recommended latest build image:

docker pull apache/doris:build-env-ldb-toolchain-latest

2. Start a container with this image and enter it.
3. Check the Maven version inside the container:

mvn -version

4. Build Doris master:

bash build.sh

5. The build fails in the FE phase because Maven 3.6.3 does not satisfy the required version range [3.9.0,).

Anything Else?

The current Docker compilation guide maps master to apache/doris:build-env-ldb-toolchain-latest, so this image appears to be out of sync with the current FE build requirement.

Build error:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.6.2:enforce (enforce-maven-version) on project fe:
[ERROR] Rule 0: org.apache.maven.enforcer.rules.version.RequireMavenVersion failed with message:
[ERROR] Detected Maven Version: 3.6.3 is not in the allowed range [3.9.0,).
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[jonathanhu237]

I worked around this locally by manually installing Maven 3.9.9 inside the container:

cd /opt
wget https://archive.apache.org/dist/maven/maven-3/3.9.9/binaries/apache-maven-3.9.9-bin.tar.gz
tar xzf apache-maven-3.9.9-bin.tar.gz
export PATH=/opt/apache-maven-3.9.9/bin:$PATH

After this, bash build.sh completes successfully, which confirms that upgrading Maven to 3.9.9 is enough to fix the issue.

I'd like to send a PR so future users don't need this workaround. While preparing it, I noticed that both build-env Dockerfiles pin Maven 3.6.3, and they use different download sources:

1. docker/compilation/Dockerfile (x86_64) downloads from the Doris-maintained COS bucket:
   https://doris-thirdparty-1308700295.cos.ap-beijing.myqcloud.com/tools/apache-maven-3.6.3-bin.tar.gz

2. docker/compilation/arm/Dockerfile (ARM64) downloads from dlcdn.apache.org.

For (1), I don't have access to the COS bucket, so I can't upload the 3.9.9 tarball myself. Could someone with access upload apache-maven-3.9.9-bin.tar.gz to the same location? Once it's there, I'll bump the version number in the Dockerfile.

For (2), one thing to be aware of: dlcdn.apache.org only hosts the current Maven release. Older versions are removed when a new one is published, so the URL will eventually 404. Would you prefer to also mirror Maven 3.9.9 to the COS bucket for consistency with x86_64, or switch the ARM Dockerfile to archive.apache.org (which keeps all historical versions permanently)?

Happy to update the PR based on your preference. Thanks!