On Jul 1, 4:49 pm, Paul Moore <p.f.mo...@gmail.com> wrote: > (My biggest concern about an uberjar is that I end up with each app > having a separate bundled copy of all its dependencies. That makes > version management a huge pain - imagine a bugfix release of > clojure.jar - but is otherwise not an unreasonable option). > > Paul.
In my former life in a Java shop, that's what we ended up doing: Bundling everything with every app, up to and including Java. You may notice that this is what apps like NetBeans and Eclipse are doing as well. Because the alternative is worse: Do you really want to depend on whatever random version of Java or external libraries a user may or may not have installed on their computer? What do you do when app A needs lib-1.1 while your new and improved app B needs lib-1.2, but lib-1.2 unfortunately breaks app A? It's the Java version of the "DLL Hell" in early Windows. I'm not up to date with developments since Java 1.5, but I expect that bundling everything with every app is still the cleanest option overall. At least for standalone applications. If it is more like a bundle of utilities that get upgraded all at once or not at all, it makes sense to treat them as one app that shares the same set of resources. jf -- 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
