It sounds like the vast majority of these apps will simply sit on the shelf, with no need to ever run them again. So, as long as you have a way to run them at need, in an accurate and acceptably prompt manner, you don't have to worry about porting the code.
So, if you can keep a Clojure 1.2 environment around _forever_, this may be a plausible strategy. One way of doing this might be to create a VM (eg, using VirtualBox) with all of the necessary apps, libraries, programs, etc. Burn this onto several CDs and save them in various locations. However, if you have to take an existing app and upgrade it in some manner, you will probably want to upgrade the version of Clojure at the same time. In support of this, you might want to find a way to create a mechanized way to recognize "issues we have seen before", so that you can get a jump start on upgrading each revived app. -r -- http://www.cfcl.com/rdm Rich Morin r...@cfcl.com http://www.cfcl.com/rdm/resume San Bruno, CA, USA +1 650-873-7841 Software system design, development, and documentation -- -- 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.
