[
https://issues.apache.org/jira/browse/HBASE-22997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926803#comment-16926803
]
stack commented on HBASE-22997:
-------------------------------
I still get the below w/ this patch in place:
{code}
+ mvn -B --settings
//Users/stack/checkouts/hbase-operator-tools/dev-support/create-release/hbase-repo-uZxSi/tmp-settings.xml
install assembly:single -DskipTests -Dcheckstyle.skip=true -Papache-release
-Prelease -
Dmaven.repo.local=/Users/stack/checkouts/hbase-operator-tools/dev-support/create-release/hbase-repo-uZxSi
.....
09:31:28 [INFO] --- maven-enforcer-plugin:1.4:enforce
(min-maven-min-java-banned-xerces) @ hbase-hbck2 ---
09:31:31 [INFO] Restricted to JDK 1.8 yet
org.apache.logging.log4j:log4j-api:jar:2.11.1:compile contains
META-INF/versions/9/module-info.class targeted to JDK 1.9
09:31:32 [WARNING] Rule 3:
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.apache.logging.log4j:log4j-api:jar:2.11.1
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
{code}
Trying to figure why...
> Move to SLF4J
> -------------
>
> Key: HBASE-22997
> URL: https://issues.apache.org/jira/browse/HBASE-22997
> Project: HBase
> Issue Type: Sub-task
> Components: hbase-operator-tools
> Affects Versions: operator-1.0.0
> Reporter: Peter Somogyi
> Assignee: Peter Somogyi
> Priority: Major
> Fix For: operator-1.0.0
>
>
> Currently hbase-operator-tools uses org.apache.logging.log4j while the rest
> of our projects have SLF4J.
> When building the project with release profile the enforce plugin fails on
> org.apache.logging.log4j:log4j-api:jar:2.11.1 dependency
> {noformat}
> [INFO] --- maven-enforcer-plugin:1.4:enforce
> (min-maven-min-java-banned-xerces) @ hbase-hbck2 ---
> [INFO] Restricted to JDK 1.8 yet
> org.apache.logging.log4j:log4j-api:jar:2.11.1:compile contains
> META-INF/versions/9/module-info.class targeted to JDK 1.9
> [WARNING] Rule 3: 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.apache.logging.log4j:log4j-api:jar:2.11.1
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
