You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Tzu-Li (Gordon) Tai (Jira)" <ji...@apache.org> on 2020/02/04 04:05:00 UTC
[jira] [Commented] (FLINK-15842) Building Stateful Functions with
JDK 11 fails due to outdated Spotbugs version
[ https://issues.apache.org/jira/browse/FLINK-15842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029549#comment-17029549 ]
Tzu-Li (Gordon) Tai commented on FLINK-15842:
---------------------------------------------
FIxed in {{master}} via 801d1b1a1306cce7e36e0d930f42f686bae2aad7
> Building Stateful Functions with JDK 11 fails due to outdated Spotbugs version
> ------------------------------------------------------------------------------
>
> Key: FLINK-15842
> URL: https://issues.apache.org/jira/browse/FLINK-15842
> Project: Flink
> Issue Type: Bug
> Components: Stateful Functions
> Affects Versions: statefun-1.1
> Reporter: Tzu-Li (Gordon) Tai
> Assignee: Tzu-Li (Gordon) Tai
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When building with JDK 11, the build fails with this:
> {code}
> [java] WARNING: An illegal reflective access operation has occurred
> [java] WARNING: Illegal reflective access by org.dom4j.io.SAXContentHandler (file:/home/shannon/ws/javaxmail-spotbugs/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar) to method com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser$LocatorProxy.getEncoding()
> [java] WARNING: Please consider reporting this to the maintainers of org.dom4j.io.SAXContentHandler
> [java] WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> [java] WARNING: All illegal access operations will be denied in future versions
> {code}
> According to https://github.com/spotbugs/spotbugs/issues/499, this is because the current Spotbugs version we use (3.1.1) uses an outdated Dom4j version.
> Upgrading to the latest Spotbugs stable version (3.1.12) fixes this issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)