If you truly have "thousands" of Clojure 1.2 apps, I'd go with option 1), and look at migrating legacy reports over if you need to do any maintenance on them. Since Clojure is "just" a Java library, it's fairly easy to keep the Clojure version locked in each individual project so there's no reason to migrate old, working reports if you don't have to do any maintenance / updates on them.
The differences in numerics as well as the difference between monolithic contrib and modern, modular contrib could eat up a lot of your time in migration and, unless you are constantly updating all those reports, I'm not sure what the benefits would be. Sean On Sun, Dec 22, 2013 at 3:51 PM, <solo.l...@gmail.com> wrote: > At my company, we use Clojure for reporting. Specifically, reports are > written in Clojure which integrate data from a variety of sources and > display the final output to the user in a WPF-based webapp. > > For all intents and purposes, each 'report' is a standalone Clojure app, and > most of them use the contrib library. Not all of them are active, but there > are thousands. And I need to migrate them over to 1.5. > > Now I know the contrib libraries are not compatible with 1.3+. From what > I've read, the big change is related to dynamic var declaration, and there > are subtle incompatibilities involving certain scalars. I also looked at > this page for information on each library's migration: > http://dev.clojure.org/display/community/Where+Did+Clojure.Contrib+Go > > I'm considering one of two approaches: > > 1) Run both Clojure 1.2 and 1.5, with all new reports required to use the > modular contrib libraries. This would require a change to the backend > appservers. > > 2) Grep the reports and create a list of all the distinct contrib libraries > we use. Identify which of the libraries have a modular analog, and replace > accordingly. To do this, I would need to check that the function signatures > match and the output is remains as expected. I would also still need to run > 1.2 running in production and 1.5 in a sandbox to migrate reports over > gradually. > > Asking individual authors to update their reports won't work. > > Please share your opinions on these approaches or what your experience was > in migrating from 1.2 to 1.3+. > > Also, is there an easier way which I'm not seeing? Thank you. > > Sol > > > > > > -- > -- > 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 unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ World Singles, LLC. -- http://worldsingles.com/ "Perfection is the enemy of the good." -- Gustave Flaubert, French realist novelist (1821-1880) -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
