[HOT-FIX][SPARK-28961][BUILD] Upgrade Maven from 3.6.1 to 3.6.2

[gatorsmile]

What changes were proposed in this pull request?

This PR is to upgrade the maven dependence from 3.6.1 to 3.6.2.

Why are the changes needed?

All the builds are broken because 3.6.1 is not available. http://ftp.wayne.edu/apache//maven/maven-3/

• https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Compile/job/spark-master-compile-maven-hadoop-3.2/485/
• https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Compile/job/spark-master-compile-maven-hadoop-2.7/10536/

Does this PR introduce any user-facing change?

No

How was this patch tested?

N/A

[gatorsmile]

cc @zsxwing

[zsxwing]

@gatorsmile have you tried locally? If it passes locally, we can just merge this. The worst case is master is still broken.

[gatorsmile]

[gatorsmile]

It already passed.

[gatorsmile]

Let me merge it now

[srowen]

It's fine to update Maven, so this is OK.

The problem is really that mirrors are only supposed to host the latest releases, and that's what build/mvn is checking. It doesn't fall back to https://archive.apache.org/dist/maven/maven-3/3.6.1/binaries/ for example, where all releases are still held.

It's a good idea to use mirrors of course. Hm, but that's going to be a problem for anyone using previous releases that refer to maintenance releases that go away from the mirror. I'll put something together to try to fall back to archive.apache.org

[dongjoon-hyun]

Thank you for the quick fix, @gatorsmile .

[srowen]

See #25667 for a change that should help avoid this going forward.

[SparkQA]

Test build #110049 has finished for PR 25665 at commit dc39d0d.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds no public classes.