I use mvn -X to diagnose such issues. mvn can also produce detailed reports on dependency and much more (mvn site -- I think).
HTH On Fri, Feb 3, 2012 at 9:19 AM, Tassilo Horn <tass...@member.fsf.org> wrote: > Stuart Sierra <the.stuart.sie...@gmail.com> writes: > > Hi Stu, > >> Clojure 1.4 goes beta! This release is essentially the same as >> 1.4.0-alpha5. It will hit the Maven Central repository in a few >> hours. > > Great news, I'd very much like to test-drive it before the 1.4.0 > release. Is there anything better than downloading its JAR and > replacing the clojure-1.3.0.jar in my project with it? > > As soon as I change my [org.clojure/clojure "1.3.0"] dependency to > "1.4.0-alpha5" (beta1 seems not have arrived yet) or "[1.3.0,)", maven > gets messed up when fetching dependencies... > > Right now, my minimized test project deps are > > :dependencies [[org.clojure/clojure "1.3.0"] > [ordered "0.3.0"] > [org.clojure/tools.macro "[0.1.1,)"]] > > which works fine. Now I've seen that ordered-1.0.0 is out. That still > works fine. > > :dependencies [[org.clojure/clojure "1.3.0"] > [ordered "1.0.0"] > [org.clojure/tools.macro "[0.1.1,)"]] > > Now trying to get the clojure snapshot breaks maven's dependency > management. > > :dependencies [[org.clojure/clojure "1.4.0-alpha5"] > [ordered "1.0.0"] > [org.clojure/tools.macro "[0.1.1,)"]] > > It errors because it couldn't download > org.clojure:clojure:jar:1.3.0-alpha5. But why 1.3.0-alpha5?!? > > Strangely, when reverting my test project to an older ordered version, > it works fine again. > > :dependencies [[org.clojure/clojure "1.4.0-alpha5"] > [ordered "0.3.0"] > [org.clojure/tools.macro "[0.1.1,)"]] > > Argh, I'll never understand maven. Is there something option to make it > show the dependency tree? I mean, tools.macro doesn't seem to have any > dependencies declared and ordered 1.0.0 has clojure "[1.2.0,1.3.0]" as > dependency. But why on earth does maven then try to get 1.3.0-alpha5? > > And is there a way to influence external deps? For example, I'm pretty > sure that the ordered library works just fine with 1.4.0. Currently, it > seems to me that in order to upgrade my own project to 1.4.0, I have to > wait until all my dependencies also added 1.4.0 as a allowed dependency, > which might take ages and hinders early test-driving and adoption of new > clojure releases. > > Sorry, that mail was not intended to become a long rant. But I'm really > interested to know how others deal with the "maven hell". > > Bye, > Tassilo > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with your > first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en -- (praki) -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
