accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3947) Use build tools to disallow log4j
Date Wed, 29 Jul 2015 19:19:05 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646627#comment-14646627
] 

Mike Drob commented on ACCUMULO-3947:
-------------------------------------

Sure. Presumably there would be other imports that we want to disallow in the future, like
if we have multiple JSON or XML parsing libraries available (via transitive dependencies)
then we could enforce consistency there too. Or multiple StringUtils imports hanging around
(guava v. apache-commons v. hadoop v. our own)

I've also seen forbidden api tool used to enforce String/byte[] conversions not using default
charset, which we do through checkstyle. Some thing I've seen it do that I'm not sure checkstyle
is easily capable of is enforce that new threads always have descriptive names and that test
assertions always have failure messages. That all could be follow on work, though.

> Use build tools to disallow log4j
> ---------------------------------
>
>                 Key: ACCUMULO-3947
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3947
>             Project: Accumulo
>          Issue Type: Task
>          Components: build
>            Reporter: Mike Drob
>              Labels: beginner
>             Fix For: 2.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message