Hi Yuri, I followed to the CLJ bug and as far as I understood Alex said that clojure is not related to this. This is also my thinking. NTF has different semantics regarding file locking than linux. And I guess that's the problem, probably the adzerk team never tried it on windows themselves.
Despite that I just gave it a try with 1.8.0-RC4 and the same error occurs. Best Regards, Sven Am Samstag, 26. Dezember 2015 14:55:30 UTC+1 schrieb Yuri Steinschreiber: > > From what I understand by looking at the Boot file access bugs, they are > actually Clojure problems (open file leaks) fixed in 1.8, so you might want > to give it a try using 1.8 Release Candidate. > > Cheers………………..Yuri > > > *From: *'Sven Richter' via ClojureScript <javascript:> > *Sent: *Friday, December 25, 2015 1:08 PM > *To: *Clojure <javascript:> > *Cc: *clojur...@googlegroups.com <javascript:> > *Subject: *Re: [ClojureScript] Re: [ANN] modern-cljs - 17th tutorial - > REPLing with Enlive > > > > Hm, > > Thats interesting, the first time I tried boot (when it was officially > anounced) on W7 it did not work for me (one of the already existing issues > hit me). > As I read this announcement here I tried it again, before writing my > answer. > What I did was to to install the latest boot and clone: > https://github.com/martinklepsch/tenzing and then run boot dev in the > repl. > After changing the only cljs file the File*Access*Exception occured. Again > this was on W7. > > Maybe they changed something within the file access code in W10. > > Still I want to argue that a lot of business runs on Windows, especially > development environments. Especially given the fact the the JVM runs on > many different platforms I would prefer that also the clojure tooling runs > on these platforms. > > Of course this is only my opinion, but still I am concerned about that > move. > > Best Regards, > Sven > > Am Freitag, 25. Dezember 2015 18:02:28 UTC+1 schrieb Sean Corfield: > > Sven Richter wrote on Wednesday, December 23, 2015 at 11:33 PM: > > While I appreciate everyones work and also like boots approach to building > clojure libs I want to remind you that boot still does not work on windows. > > > > I’ve been using Boot extensively on Windows 10 for the last few weeks and > it seems to work pretty flawlessly. The only glitch I’ve seen is in Git > Bash where `boot repl` hangs (it works perfectly in the regular CMD window). > > > > Whilst my main development setup is OS X — and I agree that the Clojure > ecosystem in general favors *nix-like environments — I’ve done almost all > my Boot learning on my Windows 10 laptop while watching TV in the evenings, > including developing the boot-expectations library (to run Expectations in > a pod in Boot), before embarking on using Boot on OS X for work (we have > almost completed a switch from Leiningen to Boot — I’m expecting it to be > fully complete on dev/QA today). > > > > Sean > > > > -- > Note that posts from new members are moderated - please be patient with > your first post. > --- > You received this message because you are subscribed to the Google Groups > "ClojureScript" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojurescrip...@googlegroups.com <javascript:>. > To post to this group, send email to clojur...@googlegroups.com > <javascript:>. > Visit this group at https://groups.google.com/group/clojurescript. > > > -- 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.