On Monday, May 4, 2015 at 4:41:02 AM UTC-4, Sven Richter wrote: > One potential problem with this "web framework" as app template approach > is upgrade-ability. When 2.0 of your "framework" comes out, what happens > to an app generated from 1.0 that wants to benefit from the new > capabilities? >
This is the reason I don't use Luminus or Modularity or others that rely heavily on leiningen template-based codegen. Its very difficult to upgrade the generated code, especially if you've had to add to or modify it. I'm experimenting with an approach that would generate only the project.clj file and directory structure (putting everything else into libraries), but don't yet have anything to release (my code is currently very targeted at my own use case, but in time I'd like to generalize it a bit and let others at it). -- 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/d/optout.
