Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/307#issuecomment-39418061
Actually, looking at this a little deeper, the smarter move might be to
bump our Guava version to 16.0.1 and eliminate the explicit dependency on
findbugs entirely. The findbugs dependency is <optional> in the 16.0.x
POM, so that should work. Furthermore, if we want to eliminate fastutil
and start using Guava more (for murmurhash3 and maybe other stuff), then
getting current with Guava makes sense (and shouldn't be a problem since we
barely use Guava at all right now.)
On Wed, Apr 2, 2014 at 10:49 PM, Mark Hamstra <markhams...@gmail.com> wrote:
> Looks like we started pulling it in with Guava:
>
>
>
https://github.com/apache/spark/commit/04567a1771ec02e1efcc3ce078291a975fbb4e68#diff-c3580fe26fb42eb3aac6e180ae11e947
> https://code.google.com/p/guava-libraries/issues/detail?id=1096
>
>
> On Wed, Apr 2, 2014 at 10:31 PM, Patrick Wendell <notificati...@github.com
> > wrote:
>
>> Seems reasonable - just wondering though - what do we use this for? I
>> think at present we aren't using this in the jenkins build... not sure
how
>> it is supposed to be used.
>>
>> --
>> Reply to this email directly or view it on
GitHub<https://github.com/apache/spark/pull/307#issuecomment-39414237>
>> .
>>
>
>
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
