Are you sure it's pulling the last tools.analyzer version? That warning has been disabled by this commit in tools.analyzer https://github.com/clojure/tools.analyzer/commit/89d98b688448fe3d02bcabea240bcb2f6d2bbd70 which is two months old
Nicola Sean Corfield writes: > Thanx for Eastwood - it's a great tool! > > Just FYI, using Clojure 1.6.0 builds produces these warnings: > > WARNING: record? already refers to: #'clojure.core/record? in namespace: > clojure.tools.analyzer.utils, being replaced by: > #'clojure.tools.analyzer.utils/record? > WARNING: record? already refers to: #'clojure.core/record? in namespace: > clojure.tools.analyzer, being replaced by: > #'clojure.tools.analyzer.utils/record? > > We've had to disable :wrong-arity due to our use of java.jdbc / congomongo > but our code - including all our Expectations tests - is clean of lint > otherwise! > > Sean > > On Mar 20, 2014, at 8:02 AM, Andy Fingerhut <andy.finger...@gmail.com> wrote: >> Eastwood is a Clojure lint tool. It analyzes Clojure source code in >> Leiningen projects, reporting things that may be errors. >> >> Installation instructions are in the documentation here: >> >> https://github.com/jonase/eastwood/#installation--quick-usage >> >> The previous release was in January 2014. Updates since then are described >> in the change log here: >> >> >> https://github.com/jonase/eastwood/blob/master/changes.md#changes-from-version-010-to-011 >> >> Probably the most noticeable changes for Eastwood users will be the errors >> if namespace/file name inconsistencies are found, and the reduction in bad >> reflection warnings. >> >> Below is the description Eastwood from the January 2014 release: >> >> For example, did you know that if you use clojure.test to write tests, and >> have multiple deftest definitions in the same namespace with the same name, >> then the tests in all but the last deftest will never be run, whether those >> tests would pass or fail? Eastwood can find those duplicate names, as well >> as other occurrences of the same Var name defined more than once. >> >> Eastwood can also warn about misplaced doc strings, calling deprecated >> functions or Java methods, expressions that are suspicious because they >> always return the same value (e.g. (= expr) is always true), expressions >> whose return value is not used and appear to have no side effects, and a few >> others. See the documentation linked above for a complete list. >> >> Jonas Enlund wrote the original version of Eastwood with the help of several >> other contributors. Version 0.1.1 is an update by Jonas, Nicola Mometto, >> and myself. It uses the new Clojure contrib libraries tools.reader for >> reading the code, and tools.analyzer and tools.analyzer.jvm for parsing the >> source into abstract syntax trees, making it straightforward to write many >> of the linters. Thanks especially to Nicola Mometto for tireless >> enhancements and bug fixes to those libraries. >> >> You can file issues on the Github issue tracker if you encounter problems, >> but please read the "Known Issues" section of the documentation before >> filing problems. Several issues have already been discovered, and their >> causes documented, while testing Eastwood on most of the Clojure contrib >> libraries, Clojure itself, and over 35 other open source libraries. >> >> Go squash some bugs! >> >> Andy Fingerhut -- 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.
