On Jul 6, 2015, at 8:58 AM, gingersafflo...@gmail.com wrote:
Thanks for this. I can go through my code and try to remove all of the uses
of JodaTime in my own code, but, as that would be some work, I'd like to
first confirm the diagnoses. Can you think of a way I might be able to
confirm
Sean Corfield,
Thanks for this. I can go through my code and try to remove all of the uses
of JodaTime in my own code, but, as that would be some work, I'd like to
first confirm the diagnoses. Can you think of a way I might be able to
confirm that Joda is, in fact, the problem?
On Jul 6, 2015, at 1058, gingersafflo...@gmail.com wrote:
Sean Corfield,
Thanks for this. I can go through my code and try to remove all of the uses
of JodaTime in my own code, but, as that would be some work, I'd like to
first confirm the diagnoses. Can you think of a way I might be
Also, your last error (about in-ns) is from an incompatible version of
clj-time, not joda-time.
By the way, this has nothing to do with interop, it's straight dependency
management on the jvm.
Concerning FD's solution of classloaders, you'll also jave to figure out a
way to package the different
Assuming there is a version that works for both dependencies, you can
manually fix it in your own project.clj. Your own direct dependencies
will override transitive ones.
Otherwise, as far as I can tell, you're stuck. Maybe you can try using
an older clj-time?
On 29 June 2015 at 21:00,
I think I have a conflict involving different libraries using different
versions of JodaTime. I have no idea how to fix this.
I have nearly the same problem as this:
http://stackoverflow.com/questions/21487476/maven-build-throws-jodatime-exception-at-runtime
However, in my case, I'm
Otherwise, as far as I can tell, you're stuck. Maybe you can try using
an older clj-time?
That's an interesting idea. I see that this:
[clj-time 0.4.5]
rolls back JodaTime to 2.1:
https://clojars.org/clj-time/versions/0.4.5
which is the same dependency as in the Java
Have you actually tried any of the exclusions that Leiningen suggests? For
example:
[clj-time 0.6.0]
overrides
[ring 1.4.0-RC1] - [ring/ring-jetty-adapter 1.4.0-RC1] - [ring/ring-core
1.4.0-RC1] - [clj-time 0.9.0]
and
[ring 1.4.0-RC1] - [ring/ring-devel 1.4.0-RC1] - [ring/ring-core
If the worst comes to the worst, you may need to run the NLP module
and the Clojure code in separate JVMs using some form of IPC to exchange
data.
That is what I'm looking at right now, though I've also been told that I
absolutely must have this working by tomorrow morning, so I'm a little
But we had this working, so I don't think the conflict is between the NLP
and the web app which uses Compojure.
On Monday, June 29, 2015 at 6:38:40 PM UTC-4, Gary Verhaegen wrote:
Assuming there is a version that works for both dependencies, you can
manually fix it in your own
On Monday, June 29, 2015 at 6:38:40 PM UTC-4, Gary Verhaegen wrote:
Assuming there is a version that works for both dependencies, you can
manually fix it in your own project.clj. Your own direct dependencies
will override transitive ones.
Otherwise, as far as I can tell, you're stuck.
11 matches
Mail list logo
