You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Andras Salamon (JIRA)" <ji...@apache.org> on 2019/04/05 07:57:00 UTC

[jira] [Commented] (OOZIE-1169) Investigate replacing ParamChecker with Google Guava's Preconditions

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

Andras Salamon commented on OOZIE-1169:
---------------------------------------

It seems to me, Oozie still use its own ParamChecker, but already started to use Guava's Preconditions as well.

> Investigate replacing ParamChecker with Google Guava's Preconditions
> --------------------------------------------------------------------
>
>                 Key: OOZIE-1169
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1169
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: trunk
>            Reporter: Robert Kanter
>            Priority: Minor
>
> We currently use our own {{ParamChecker}} class to check/verify arguments for some of the methods.  We should investigate if it makes sense to use [Google Guava's Preconditions|http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/base/Preconditions.html] instead (or some other library).  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)