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

ASF GitHub Bot commented on METRON-1430:
----------------------------------------

Github user cestella commented on the issue:

    https://github.com/apache/metron/pull/910
  
    Yeah, this is the first step to moving it out, I'd say.  This was useful 
independent of #907 because it made some things a lot cleaner (namely fewer 
`new TypeReference<Map<String, Object>>() {}` and more 
`JSONUtils.MAP_SUPPLIER`).


> Isolate jackson from being used as arguments or returns from JSONUtils
> ----------------------------------------------------------------------
>
>                 Key: METRON-1430
>                 URL: https://issues.apache.org/jira/browse/METRON-1430
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: Casey Stella
>            Priority: Major
>
> Currently jackson is used as part of our internal API to JSONUtils.  The 
> problem here is when we shade and relocate jackson.  Suddenly we can't use 
> JSONUtils.  We should avoid operating on jackson primitives and rather 
> provide a convenient wrapper around the places where we use jackson as part 
> of the API.



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

Reply via email to