I concur, but maybe we could make a second release of the closure lib main jar, with a dependency on third-party? That would reflect the actual dependency.
I know, you asked for testing before the release. Sorry for not catching this one. 2012/11/13 Stuart Sierra <the.stuart.sie...@gmail.com> > My original reason for splitting the third-party JAR was the licensing: > the main G.Closure library is under the Apache license; the third-party > libraries are under a variety of different licenses. > > One simple solution would be to make ClojureScript itself have a > dependency on the third-party libs in addition to the core G.Closure > libraries. Then users would still have the option of excluding the > third-party extensions from their projects. > > -S > > > -- > 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 > -- 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
