ORC-1001: Bump maven-enforcer-plugin to 3.0.0

[autumnust]

What changes were proposed in this pull request?

While working on another PR, I found the head of main failed in GA with the failure like below.

Error:  -----------------------------------------------------
Error:  realm =    plugin>org.apache.maven.plugins:maven-enforcer-plugin:1.4.1
Error:  strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
Error:  urls[0] = file:/Users/runner/.m2/repository/org/apache/maven/plugins/maven-enforcer-plugin/1.4.1/maven-enforcer-plugin-1.4.1.jar
...
Error:  Number of foreign imports: 1
Error:  import: Entry[import  from realm ClassRealm[maven.api, parent: null]]
Error:  
Error:  -----------------------------------------------------: begin 0, end 3, length 2
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/PluginContainerException
make[2]: *** [java/shims/orc-shims-1.8.0-SNAPSHOT.jar] Error 1
make[1]: *** [java/CMakeFiles/java_build.dir/all] Error 2
make: *** [all] Error 2
Error: Process completed with exit code 2.

Google a bit and found a similar issue: apache/accumulo-proxy#19
This PR is a draft to see if the same change could work here ( since I don't have specific env like failed CI)

Why are the changes needed?

Recover compile and package without tests.

How was this patch tested?

Manual.

mvn compile
mvn package -DskipTests

[guiyanakuang]

I think the JDK17 General-Availability Release was released two days ago. Github workflow updated JDK17. Now System.getProperty("java.version") returns "17" which causes a lot of program exceptions.

Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
Maven home: /usr/share/apache-maven-3.8.2
Java version: 17, vendor: Azul Systems, Inc., runtime: /opt/hostedtoolcache/jdk/17.0.0/x64

For example org.apache.hadoop.util.Shell.java

private static boolean IS_JAVA7_OR_ABOVE =
      System.getProperty("java.version").substring(0, 3).compareTo("1.7") >= 0;

java.lang.StringIndexOutOfBoundsException: String index out of range: 3

[dongjoon-hyun]

Oh, I didn't see your PR and made a PR to upgrade Java 17.

• ORC-1000: Use Java 17 in GitHub Action #911

[dongjoon-hyun]

Actually, this is very unfortunate situation because we released Apache ORC 1.7.0. :(

[dongjoon-hyun]

At least, I verified that this PR recover compile and package (without tests).
Thank you, @autumnust .

[dongjoon-hyun]

We can use 3.0.0.

[dongjoon-hyun]

+1, LGTM. Thank you, @autumnust and @guiyanakuang .
We can fix the issue step by step.

[guiyanakuang]

Actually, this is very unfortunate situation because we released Apache ORC 1.7.0. :(

@dongjoon-hyun, probably JDK official will fix this problem, because there are many programs involved. It should not be necessary for each program to upgrade the Java version judgment. So don't worry about the ORC 1.7.0 compatibility issue.

[dongjoon-hyun]

BTW, maven-enforcer-plugin issue exists only at main. I landed at main only.

[dongjoon-hyun]

Do you have any reference for that? Actually, Java community is a little notorious because they don't care about that many programs, @guiyanakuang .

[guiyanakuang]

@dongjoon-hyun I remember a similar thing happening with JDK 9. I always thought it was the JDK that officially solved the version number problem. I just googled it and I was wrong. : (

[dongjoon-hyun]

Oh, I misread the message and deleted my previous comment~ If you received them via the email, please forget about that.

[dongjoon-hyun]

BTW, this might be only our test framework issue. Let me dig more.

[guiyanakuang]

Yes, there is no code directly related to java version in ORC, the example I gave is from hadoop 2.2. It has been fixed at https://issues.apache.org/jira/browse/HADOOP-14586. Don't worry too much.

[dongjoon-hyun]

Ya, that could be one reason to raise the min.hadoop.version.

BTW, for Java 17 testing, I'll add a profile as a separate PR.