I could be wrong, but I think I've seen this before under these circumstances:
Clojure namespace ns-a imports Java class SomeClass. Clojure namespace ns-b requires ns-a. Clojure namespace ns-b refers to SomeClass, and everything works smoothly. Then ns-a stops importing Java class SomeClass, and ns-b starts complaining. Again, I could be making this up, but I think I remember debugging an issue just like this. ns-b only compiled in the first place by accident of loading order. On Monday, January 23, 2017 at 4:59:10 PM UTC-7, Gary Trakhman wrote: > > I've seen non-determinism across machines with regard to multiple > namespaces being searched to AOT with the clojure-maven plugin (only > noticed because it resulted in an error). The workaround was to specify a > single entry point namespace to clojure-maven and let the clojure compiler > sort out namespace dependency order. > > On Jan 23, 2017 6:24 PM, "'William Parker' via Clojure" < > clo...@googlegroups.com <javascript:>> wrote: > >> Clojure 1.8 both before and after; I should have put that in my original >> post. As far as I'm aware there were no changes of any kind in the >> environment or code between the failing state and the successful one, >> although since I don't control our CI environment it is possible there were >> environmental changes I'm not aware of (it is a large enterprise >> environment with many different teams potentially making changes). >> Unfortunately I've been unable to change anything such as JVM versions in >> my local environment to get the code to compile but I'll post back here if >> I find some such method. Without the ability to duplicate the difference >> there probably isn't much debugging that can be done but I was curious if >> there are known issues that could lead to such problems. >> >> On Monday, January 23, 2017 at 4:19:44 PM UTC-6, Alex Miller wrote: >>> >>> Most helpful would be to know what Clojure version you are on now and >>> what changed between when it didn't fail and when it did. >>> >>> There have been a variety of changes to both type hints and classloading >>> over the last few releases and it's likely that the error is now simply >>> found when it was silently not found and ignored before. >>> >>> On Monday, January 23, 2017 at 3:01:38 PM UTC-6, William Parker wrote: >>>> >>>> I have a case where JVM Clojure code like (some-> ^JavaClassA this >>>> ^FieldTypeA (.getFieldTypeA) (.getFieldTypeB)) previously compiled for a >>>> long time and suddenly just started failing in our CI system because the >>>> class FieldTypeA wasn’t imported in the namespace. I understand the need >>>> to import the class but I don’t see why it ever compiled and am wondering >>>> if there is any known nondeterminism here. I looked through the Clojure >>>> JIRA tracker but didn't find anything that seemed related. >>>> >>> -- >> You received this message because you are subscribed to the Google >> Groups "Clojure" group. >> To post to this group, send email to clo...@googlegroups.com >> <javascript:> >> Note that posts from new members are moderated - please be patient with >> your first post. >> To unsubscribe from this group, send email to >> clojure+u...@googlegroups.com <javascript:> >> 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+u...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- 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.
