>>> And might it be a
>>> good idea to be able to name .clj files instead of namespaces as an
>>> option? Then one could use regular ant filesets constucted
>>> automatically from expressions, instead of naming namespaces
>>> individually.
>
> And now this has also been added. Both the compile and
On Wed, Aug 12, 2009 at 12:03 PM, J. McConnell wrote:
> On Wed, Aug 12, 2009 at 4:00 AM, C. Florian Ebeling <
> florian.ebel...@gmail.com> wrote:
>
>>
>> Thanks for sharing this. What I miss a bit is the ability to set the
>> *compile-path* to something other than "classes".
>
>
> Thanks for your
On Mon, Aug 10, 2009 at 9:07 AM, Chas Emerick wrote:
>
> 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've added sup
On Wed, Aug 12, 2009 at 4:00 AM, C. Florian Ebeling <
florian.ebel...@gmail.com> wrote:
>
> Thanks for sharing this. What I miss a bit is the ability to set the
> *compile-path* to something other than "classes".
Thanks for your input! Yes, this was always planned, I just didn't have a
need for
Thanks for sharing this. What I miss a bit is the ability to set the
*compile-path* to something other than "classes". And might it be a
good idea to be able to name .clj files instead of namespaces as an
option? Then one could use regular ant filesets constucted
automatically from expressions, in
On Aug 10, 2009, at 11:45 AM, J. McConnell wrote:
> On Mon, Aug 10, 2009 at 9:07 AM, Chas Emerick
> 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 Task
On Mon, Aug 10, 2009 at 9:07 AM, Chas Emerick 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
I hadn't looked at the patch before, but I was delighted to see the posting
about it a few days ago. I think it will benefit everyone. However, I was
well underway with these tasks at the time (I haven't had a lot of time to
work on them, so it took a couple of weeks). Regardless, I really wanted t
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.
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 tho
Hi,
have you seen the recent patch submitted by Mike Hinchey ?
http://www.assembla.com/spaces/clojure/tickets/168
Regards,
--
Laurent
2009/8/10 J. McConnell
> 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
I haven't had a chance to try it out yet, but this is very promising. Thanks
for doing it.
On Sun, Aug 9, 2009 at 11:58 PM, Richard Newman wrote:
> On 9 Aug 2009, at 8:14 PM, J. McConnell wrote:
>
> http://github.com/jmcconnell/clojure-ant-tasks/tree/master
>
> I hope someone finds some benefit
On 9 Aug 2009, at 8:14 PM, J. McConnell wrote:
> 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.
Thanks for sharing this; I'll give it a shot (when I'm back from
vacation) and let you know h
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
13 matches
Mail list logo
