Duo Zhang created HBASE-24798:
---------------------------------
Summary: [hbase-thirdparty] Exclude module-info.class in
enforceBytecodeVersion rule
Key: HBASE-24798
URL: https://issues.apache.org/jira/browse/HBASE-24798
Project: HBase
Issue Type: Bug
Components: build, thirdparty
Reporter: Duo Zhang
Assignee: Duo Zhang
Fix For: thirdparty-3.4.0
Got this when releasing thirdparty-3.4.0.
{noformat}
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.
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
