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

Posted to notifications@ctakes.apache.org by "Sean Finan (JIRA)" <ji...@apache.org> on 2017/05/01 21:03:05 UTC

[jira] [Created] (CTAKES-444) Get rid of guava

Sean Finan created CTAKES-444:
---------------------------------

             Summary: Get rid of guava
                 Key: CTAKES-444
                 URL: https://issues.apache.org/jira/browse/CTAKES-444
             Project: cTAKES
          Issue Type: Improvement
          Components: ctakes-core
    Affects Versions: 4.0.1
            Reporter: Sean Finan
            Assignee: Sean Finan
            Priority: Minor


Everything that I have seen in ctakes that uses guava can be replaced by what now exists in java core or ctakes-core.  I haven't seen everything, but getting rid of guava module -by- module would be good.  Also, ctakes needs to stop depending upon an entire framework just to use one method instead of two. e.g. Strings.isNullOrEmpty( s ) instead of ( s == null || s.isEmpty() ).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)