CODEWITHSUNDEEP
javaguava
fishtoprecords
fishtoprecords

Reputation: 2404

Splitter blows up on simple Pattern

I am just starting to us Guava in place of Google-Collections. The Splitter class seemed cool. But when I use it, like this:

private static final Pattern p = Pattern.compile(" +");
private static final Splitter usSplitter = Splitter.on(p).trimResults();

I get a stack dump:

java.lang.NoSuchMethodError: com.google.common.base.Platform.precomputeCharMatcher(Lcom/google/common/base/CharMatcher;)Lcom/google/common/base/CharMatcher;
        at com.google.common.base.CharMatcher.precomputed(CharMatcher.java:662)
        at com.google.common.base.CharMatcher.<clinit>(CharMatcher.java:69)
        at com.google.common.base.Splitter.<init>(Splitter.java:99)
        at com.google.common.base.Splitter.on(Splitter.java:208)

The javadocs have nothing about this "com.google.common.base.Platform." so its a bit hard to guess what is going wrong.

As you can see, the Pattern is dead simple.

Upvotes: 9

Views: 4856

Answers (3)

Ashaar Riaz
Ashaar Riaz

Reputation: 31

Actually. you got two version of com.google.common.base.Platform class and one of these classes has or hasn't the method.

Try to remove one of the jar files. I suggest to remove google-collections.jar and leave gauva.jar.

It will work fine.

Upvotes: 3

ColinD
ColinD

Reputation: 110054

What version of Guava are you using? This works perfectly fine for me with r05.

Edit: It seems like the specific issue here is that you have both google-collections and guava in your runtime classpath. Platform (an internal class) existed in google-collections but didn't have the precomputedCharMatcher method. Splitter is being loaded from the guava jar properly, but Platform is being loaded from the google-collect jar.

Upvotes: 9

BalusC
BalusC

Reputation: 1108822

The java.lang.NoSuchMethodError tells you that the desired method is missing in the current runtime classpath while it was there in the compile time classpath.

In other words, to fix this problem you need to align your runtime classpath to have the correct version of the API as you used during compile time. It can also be caused by having different versions of the library mixed throughout the runtime classpath. Cleanup the classpath then.

Upvotes: 15

Related Questions