xsc / lein-ancient

Check your Projects for outdated Dependencies
MIT License
561 stars 33 forks source link

Lots of java.lang.NoSuchMethodError warnings #98

Closed joelittlejohn closed 6 years ago

joelittlejohn commented 6 years ago

I haven't yet worked out why, but for some reason when I run lein ancient on my projects using lein-ancient 0.6.15 (Leiningen 2.8.1, Clojure 1.9.0 and Java 1.8.0_151), I see a lot of output like the following:

(warn)  [releases] - Δ    2ms - failure when checking environ/environ: java.lang.NoSuchMethodError: com.amazonaws.util.StringUtils.trim(Ljava/lang/String;)Ljava/lang/String;
(warn)  [releases] - Δ    1ms - failure when checking com.codahale.metrics/metrics-logback: java.lang.NoSuchMethodError: com.amazonaws.util.StringUtils.trim(Ljava/lang/String;)Ljava/lang/String;
(warn)  [releases] - Δ    0ms - failure when checking ch.qos.logback/logback-classic: java.lang.NoSuchMethodError: com.amazonaws.util.StringUtils.trim(Ljava/lang/String;)Ljava/lang/String;
(warn)  [releases] - Δ    0ms - failure when checking clj-http/clj-http: java.lang.NoSuchMethodError: com.amazonaws.util.StringUtils.trim(Ljava/lang/String;)Ljava/lang/String;
xsc commented 6 years ago

@joelittlejohn Looks like there might be a conflicting version of the AWS SDK on your classpath. Can you paste your profiles.clj and the output of lein deps :plugin-tree?

joelittlejohn commented 6 years ago

Sorry for the noise, I had a forehead slapping moment when you mentioned the profiles.clj as I really should have checked this before creating this issue. It's something in my profiles.clj as when I moved this out of the way the warnings disappeared.

joelittlejohn commented 6 years ago

Hmm, there's something a little more going on here. When I use lein-ancient in my profiles.clj, I see the warnings. When I add it to my project directly (even when my profiles.clj is still intact) I don't see the warnings :thinking:

I'll do some more investigation and reopen this if I find any evidence that something needs to change in lein-ancient :slightly_smiling_face:

joelittlejohn commented 5 years ago

Just in case anyone else finds this, in the end my problem was this plugin [s3-wagon-private "1.2.0"]. Upgrading to [s3-wagon-private "1.3.1"] causes an upgrade of aws-java-sdk-s3 and fixes these 'failure when checking' warnings.

See also #82