[apache/helix] -- Provide JDK 1.8 (backward) compatibility of helix-core

[himanshukandwal]

Issues

• [x] My PR addresses the following Helix issues and references them in the PR description: Fixes #2779

Description

• [x] Here are some details about my PR, including screenshots of any UI changes: We have some consumers which are still running their (open-source) systems on JRE-8, hence they are not able to run helix libraries compiled with JDK11+.

We would like to provide a backward compatible support to our consumers where they also have an option to use JDK-8 compiled helix-core jar, if they have such a requirement. By default we will generate JDK-11 jars and JDK-8 jars using a classifier.

<major.minor.patch> will use JDK11 (default)
<major.minor.patch> classifier say jdk8 , will use JDK8

For JDK-11 usecase

      <dependency>
          <groupId>org.apache</groupId>
          <artifactId>helix</artifactId>
          <version>1.3.4</version>
      </dependency>

For JDK-8 usecase

      <dependency>
          <groupId>org.apache</groupId>
          <artifactId>helix</artifactId>
          <version>1.3.4</version>
          <classifier>jdk8</classifier>
      </dependency>

Tests

• [x] The following tests are written for this issue: N/A

---------------------------------------------------------------------------------------------------
mvn clean install -Dmaven.test.skip.exec=true
---------------------------------------------------------------------------------------------------
[INFO] 
[INFO] --- compiler:3.10.1:compile (JDK 8) @ helix-core ---
[WARNING]  Parameter 'outputDirectory' is read-only, must not be used in configuration
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 579 source files to /Users/hkandwal/Documents/workspaces/projects/helix_os_hk/helix-core/target/classes_jdk8
[INFO] 
[INFO] --- compiler:3.10.1:compile (JDK 11) @ helix-core ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 579 source files to /Users/hkandwal/Documents/workspaces/projects/helix_os_hk/helix-core/target/classes
[INFO] 
[INFO] --- bundle:5.1.4:manifest (bundle-manifest) @ helix-core ---
[WARNING] Manifest org.apache.helix:helix-core:bundle:1.3.2-SNAPSHOT : Unused Import-Package instructions: [org.apache.logging.log4j*, org.apache.logging.slf4j*] 
[INFO] Writing manifest: /Users/hkandwal/Documents/workspaces/projects/helix_os_hk/helix-core/target/classes/META-INF/MANIFEST.MF
[INFO] 

• The following is the result of the "mvn test" command on the appropriate module:

(If CI test fails due to known issue, please specify the issue and test PR locally. Then copy & paste the result of "mvn test" to here.)

Changes that Break Backward Compatibility (Optional)

• My PR contains changes that break backward compatibility or previous assumptions for certain methods or API. They include:

(Consider including all behavior changes for public methods or API. Also include these changes in merge description so that other developers are aware of these changes. This allows them to make relevant code changes in feature branches accounting for the new method/API behavior.)

Documentation (Optional)

• In case of new functionality, my PR adds documentation in the following wiki page:

(Link the GitHub wiki you added)

Commits

• My commits all reference appropriate Apache Helix GitHub issues in their subject lines. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters (not including Jira issue reference)
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

Code Quality

• My diff has been formatted using helix-style.xml (helix-style-intellij.xml if IntelliJ IDE is used)