Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-24798

[hbase-thirdparty] Ignore module-info and SubmissionPublisher in enforceBytecodeVersion rule

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • thirdparty-3.4.0
    • build, thirdparty
    • None
    • Reviewed
    • Hide
      Ignore module-info in enforceBytecodeVersion rule as it is for supporting for JDK9+ and will not break JDK8 support.
      Ignore SubmissionPublisher in enforceBytecodeVersion rule as it is used by jersey-common for supporting JDK11 and will not break JDK8 support.
      Jersey 2.x promises to support JDK8.
      Show
      Ignore module-info in enforceBytecodeVersion rule as it is for supporting for JDK9+ and will not break JDK8 support. Ignore SubmissionPublisher in enforceBytecodeVersion rule as it is used by jersey-common for supporting JDK11 and will not break JDK8 support. Jersey 2.x promises to support JDK8.

    Description

      Got this when releasing thirdparty-3.4.0.

      10:46:33 [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ hbase-shaded-jersey ---
      10:46:33 [INFO] Restricted to JDK 1.8 yet org.glassfish.jersey.core:jersey-common:jar:2.31:compile contains META-INF/versions/11/org/glassfish/jersey/internal/jsr166/SubmissionPublisher$1.class targeted to 55.0
      10:46:33 [INFO] Restricted to JDK 1.8 yet jakarta.ws.rs:jakarta.ws.rs-api:jar:2.1.6:compile contains module-info.class targeted to JDK 1.9
      10:46:33 [WARNING] Rule 1: org.apache.maven.plugins.enforcer.EnforceBytecodeVersion failed with message:
      HBase has unsupported dependencies.
        HBase requires that all dependencies be compiled with version 1.8 or earlier
        of the JDK to properly build from source.  You appear to be using a newer dependency. You can use
        either "mvn -version" or "mvn enforcer:display-info" to verify what version is active.
        Non-release builds can temporarily build with a newer JDK version by setting the
        'compileSource' property (eg. mvn -DcompileSource=1.8 clean package).
      Found Banned Dependency: org.glassfish.jersey.core:jersey-common:jar:2.31
      Found Banned Dependency: jakarta.ws.rs:jakarta.ws.rs-api:jar:2.1.6
      Use 'mvn dependency:tree' to locate the source of the banned dependencies.
      

      Attachments

        Issue Links

          Activity

            People

              zhangduo Duo Zhang
              zhangduo Duo Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: