I'm also running into this issue with the Jackson transitive dependency in
my application. I've submitted a ticket to Heroku support and submitted a
question to Stack Overflow http://stackoverflow.com/q/12739388/720805.
I'm new to maven and I am curious how you were able to work around this
My direct dependency is on AWS and I'm using leiningen to manage maven
dependencies, so I did this to exclude Jackson:
[com.amazonaws/aws-java-sdk 1.3.10
:exclusions [org.codehaus.jackson/jackson-core-asl
org.codehaus.jackson/jackson-mapper-asl]]
That may not help if you
The m2 cache is stored across builds on Heroku. So you need to destroy
that cache if it was corrupted or needs to be rebuilt.
Unfortunately there probably isn't a great way to do this. You could
contact support to see if they can help. Or you can fork/hack the
buildpack to do this.
Hope that
Phil Hagelberg just got back to me from Heroku Support---he thinks it's a
problem with Maven central. The Jackson packages have become inaccessible
for some reason.
I think I can work around it while they work on it because this is a
transitive dependency for me.
Thanks,
-Mike
On Tuesday,
