[
https://issues.apache.org/jira/browse/HBASE-21881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16766190#comment-16766190
]
Nihal Jain commented on HBASE-21881:
------------------------------------
{quote} I saw from HBASE-21872 that it looked like it was picking up JDK 1.6
signatures
{quote}
Yes you're right. I fixed it to:
{code:java}
<compileSource>1.8</compileSource>
.
.
<maven.compiler.source>${compileSource}</maven.compiler.source>
<maven.compiler.target>${compileSource}</maven.compiler.target>
{code}
Thanks for noticing.
{quote}Might also be worth adding commons-io.
{quote}
Thanks will add it in the bundled signatures list. Currently I have added the
following:
* jdk-unsafe
* jdk-deprecated
* jdk-non-portable
* jdk-reflection
* commons-io-unsafe-${commons-io.version}
> Use Forbidden API Checker to prevent future usages of forbidden api's
> ---------------------------------------------------------------------
>
> Key: HBASE-21881
> URL: https://issues.apache.org/jira/browse/HBASE-21881
> Project: HBase
> Issue Type: Improvement
> Components: build
> Reporter: Nihal Jain
> Assignee: Nihal Jain
> Priority: Major
>
> [Policeman's Forbidden API
> Checker|https://github.com/policeman-tools/forbidden-apis] provides an
> elegant way to fail build if any "forbidden api" is used in the code base.
> Here we will add the plugin to our pom.xml.
> We will discuss which all api's to put in forbidden list. Or whether to use
> the one's bundled with the plugin.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
