Hi,

I notice that if my project.clj specifies a dependency on Clojurescript (or on 
a Clojurescript library which in turn pulls in Clojurescript), this causes my 
project to have a dependency on the Google Closure compiler and all of its 
dependencies. If I understand this correctly, it means that stuff like Guava 
and FindBugs is on the classpath of my application at runtime and those 
libraries are included in any uberjar or uberwar that I export.

Is this necessary? Is there any need for my project to see these libraries at 
runtime and, if not, is there any way to suppress this behaviour?

The reason that this is particular importance to me right now is that i'm 
trying to deploy an uberwar of my Clojure+Clojurescript app to a WebSphere 
Liberty app server and I think I'm hitting a bug in Guava 15 (which is pulled 
in by the Google Closure compiler): [1] . I can work around this by changing my 
Clojurescript dependency to point to an earlier version of Clojurescript (which 
indirectly then depends on an earlier version of Guava that doesn't suffer from 
the bug) but there has to be a better way to make this work.

I guess this follows on from Nikita's recent question about how to specify 
Clojurescript dependencies [2]. Is there a way to specify a dependency on 
Clojurescript such that I can use it at dev time but not pull in its 
dependencies at runtime?

Cheers,
Chris

[1] https://code.google.com/p/guava-libraries/issues/detail?id=1527
[2] https://groups.google.com/forum/#!topic/clojurescript/ppGsyD0xmyw

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/clojurescript.

Reply via email to