Yes, I know. ;) In this case it's happening with an uberjar, not with the repl. I do "java -jar myapp.jar", and later, while it is processing data, get this exception. No repl involved.
On Saturday, December 6, 2014 2:02:01 PM UTC-8, juan.facorro wrote: > > Hi Brian, > > This problem usually happens when working on the REPL and you redefine a > record or type (derecord and deftype), but there are still some existing > instances lying around, that belong to the previous definition of that same > type. > > See this thread for more information: > https://groups.google.com/forum/#!msg/clojure/N2ivUM8bvB8/xgiFVtsXKnkJ > > Cheers, > > Juan > > On Saturday, December 6, 2014 5:55:23 PM UTC-3, Brian Craft wrote: >> >> I'm experimenting with jwrapper, and am getting runtime exceptions like >> this, due to some jar manipulation that it's doing. I know one of the steps >> is pack200, however running pack200 manually doesn't create these issues. >> >> Anyone have suggestions for debugging this? I've seen this type of error >> countless times in clojure, but only when reloading interactively. This is >> the first time I've see it when running an uberjar. >> > -- 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.
