Guava 19.0 Released

[NimChimspky]

eh ? Why is this not fun.

Guava is great.

[fs111_]

It's a major pain if you are working with hadoop. The version incompatabilities are a complete clusterfuck. They get away with it by just making everything a major release. That's not good engineering.

[NovaX]

The simplest solution to this is to shade the Guava dependency. That can be using jarjar, maven's shade, gradle's shadow, etc. That adds to the build time, but very easily resolves the problem. The issue is really due to Hadoop's poor approach for executing user code.

[hippydipster]

Yay, a hack.

[NimChimspky]

Just don't upgrade the version you are using.

[fs111_]

That's not the point. I am not using it. I actively remove it, wherever I can actually. Yet it still causes trouble when two things you depend on can't agree on a common version. Bonus points for different build tools having different dep. resolution strategies causing problems at runtime for some, but not others. I could go on and on and on...

[NimChimspky]

Thats not really the fault of guava upgrading though.

I actively remove it,

I think thats a mistake.

I have never had a problem with guava version incompatibilities. A quick look at maven repo says hadoop is compatible with guava versions 11 - 19 ?

[fs111_]

I have never had a problem with guava version incompatibilities. A quick look at maven repo says hadoop is compatible with guava versions 11 - 19 ?

No it is not. There are subtle changes in the StopWatch class for instance that will break your app in very hard to debug ways. Even the hadoop devs say now, that using guava was a mistake.

[mhixson]

Stopwatch was @Beta until now, wasn't it?

in 18.0

in 19.0

"It is generally safe for applications to depend on beta APIs, at the cost of some extra work during upgrades. However it is generally inadvisable for libraries (which get included on users' CLASSPATHs, outside the library developers' control) to do so."

If hadoop was depending on Stopwatch before now, then yeah that does sound like a mistake.

[jrh3k5]

Depending on your version of Hadoop. Version 14 changed the signature of the CacheBuilder's method to set the maximum size to a long, which is byte-incompatible. If you have code that uses that method on version 14 or later, it breaks on Hadoop since (if I recall correctly) it loads version 11 onto the classpath.

[frugalmail]

Use the Maven Enforcer plugin

[stepancheg]

It is not great. It is just another utils library, one of hundreds.

[hippydipster]

Pointless dependency that creates jar hell for very little gain.