Most of the Ant setups I've seen for building and testing Clojure code, including some of my own, have suffered from the fact that compilation and test failures still result in a "Successful" build in Ant's eyes. This can be confusing at best, but can cause real problems if you aren't paying close attention and have stale jars laying around from a previous build. The solution for me until now was to set up failure properties that get set when a compile or test fails, but it is a real pain to set this up for each new project.
Thus, Clojure Ant Tasks was born. This is very young at this point, but does support the building and testing of Clojure 1.0-compatible projects. After defining the tasks, you just pass them a classpath and a list of namespaces to build/test and it will do so, failing when appropriate. Despite being young, I wanted to release this now to get feedback from people with larger projects than my own. Both clojure and clojure-contrib suffer from the problem that compilation and test failures aren't reported by Ant, so it would be great to stabilize this set of tasks and be able to take advantage of them there. Patches, bug reports and feature requests are all very much welcome. The code can be checked out from here: http://github.com/jmcconnell/clojure-ant-tasks/tree/master I hope someone finds some benefit from these. Let me know if you have any questions. Regards, - J. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
