On Mon, Aug 10, 2009 at 9:07 AM, Chas Emerick <cemer...@snowtide.com> wrote:
> Looks like a good start. I initially didn't grok what was going on, until > I realized that you were aiming for an "actual" ant library. > Yes, I wasn't very familiar with Ant Tasks (as in org.apache.tools.ant.Task) or macros until I looked into this, but I already had a few lines of Clojure code that I was using to detect test failures that I wanted to make use of for better reporting. So, I figured I'd go the Task route using gen-class. I imagine the fact that the tasks are written in Clojure will prove useful in terms of tighter integration with clojure.test and whatnot in the future. > We have a couple of ant macros that do all of our clojure building for us > (including auto-detecting namespaces within source directories, compiling > only those clojure files that have changed since the last build, etc). I > wonder if there'd be space for us to add those to this though, as its > charter and approach are pretty different than just "a couple of macros" :-) > Hmmm ... like I said, I'm not really familiar with Ant macros (though perhaps I should be), but it'd be nice if this could work. Perhaps a macro could generate the list of namespaces to compile/test and pass that to the task? Eventually the task should probably support both of those features, definitely the latter. Maybe I can make it down to one of the Western Mass Dev meetings one of these days (I'm in North Adams) and we can hack something up :) 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 -~----------~----~----~----~------~----~------~--~---
