I'd vote to exclude and pull in ours and then test that it still functions. I'd say that having the integration tests function should give a decent idea if it'll work in vagrant, but of course we should run it up in vagrant as well.
Casey On Wed, Feb 22, 2017 at 6:07 AM, Justin Leet <justinjl...@gmail.com> wrote: > Long story short, geoip2 lib behaves badly and one of its dependencies > pulls in an open ended range of jackson-databind which is breaking our > build as it tries to pull in 2.9.0-SNAPSHOT. See: > https://github.com/maxmind/GeoIP2-java/issues/77 > > As noted in that thread, the easy solution is to just <exclude> jackson and > pull in ours. The catch is that geoip2 specifies a slightly higher version > of jackson than we globally use (2.8.x instead of 2.7.x). Adding the > exclusion does allow for compiling, but I haven't tested anything. > > I'd like to get thoughts on our preferred way to fix this. E.g. add the > exclusion alone and test? Bump the jackson version in enrichments > specifically and test? bump the whole version and test? > > Ticket to track > https://issues.apache.org/jira/browse/METRON-734 > > Thanks, Justin >
